Amazfit Watch faces

Of course it's going to cause an error. Because if you look at the structure of the files before changing them, you will see that it is different. In the best case you can copy the init_view() function from one file to another. But you also need to m,eltn copy other elements besides the function.

piotarock
1. The editor makes watch faces on API 1. In Zeus CLI you have created code on API 2. They have fundamentally different code and cannot be copied. Create a watch face on API 1. If it is important for your design to use functions that are available only on API 2, you can take only ...

It seems to be a specific feature of this model. You can try to use ‘Numeric values’ image set instead of font. It might help.

Because there's no such thing in the editor. You have to edit the code of the finished watch face.
You cannot display calendar events on the watch face. You can only add a shortcut to the calendar.

I think they make a blank watch face in the official editor and export it to .zab. Then in it they change the existing .zpk file to the .zpk file created in my editor.

When using Zeus CLI, it also creates an empty watch face and then pastes the code from the watch face created in the editor into it ...

It seems that if you select a custom preview instead of a generated preview when exporting, it works faster. But I'm not sure.

This is an example I've created; it's the simplest method I can think of.
But you need to create a 60-frame image to show this progress.

This is the simplest option and the easiest to adapt to different models.
But you can also make one image with the background as a mask. And under it, place ...

I find the issue caused by, and I can push some watchfaces to the official simulator :D
(Example watchface: Marc F18 Golf FR V1 ( https://amazfitwatchfaces.com/active/view/1737 ) made by markillers ( https://amazfitwatchfaces.com/ucp/871122 ))
https://i.postimg.cc/pTPLZ7ph/ying-mu-xie-qu-hua-mian ...

A useful utility.
If you’re interested, we could discuss the possibility of integrating it into the editor. That way, you wouldn’t need to go through the process of unpacking the dial; you could simply work with the pre-prepared files.

After dive in the JSON file, I discovered that the simulator uses socket.io to communication with the CLI.

Fortunately, NuGet has the package uses the same protocol, is available for C#.

https://github.com/doghappy/socket.io-client-csharp

Using that NuGet package, along with my limited C ...

I uploaded the polished version here:
https://github.com/Bob-YsPan/zepp-os-pu ... mulator-cs

Spoiler

Maybe this version is easier to merge into the Editor, it eliminates the dependency on Node.js.

I find out the package exported by the SashaCX75's WatchFace editor, can push into the simulator with little modification:

Edit: I added the flow into the C#'s version of the program, just open the exported watchface package like the zpk!

(Steps 1~2 can see the instruction in this README https ...

I successfully imported the dial I created in the editor into the simulator.
I honestly didn't understand the point of step 2 in your instructions. I just replaced the images in the dial file with standard PNG files and everything worked.

Since you’ve rewritten the code in C#, I should probably be ...

If you want to keep your utility as a standalone app, I have a few suggestions.
Take the app.json file from the watch face archive rather than selecting it as a separate file. Instead of using the DeviceSource code, specify the exact model; this makes it clearer. If possible, allow users to select ...

When using dials from the GTR 3 Pro, the animation and smooth second hand will most likely not work. The rest of the functions should be identical.

@Sharpshot90
Here are the test dials to check if the colours are correct. One is created in my editor, the other in the official editor. See how they are displayed on AOD.

BigBlind68 If there is animation in the watch face, you can try to set the GTR 4 model in the editor before building.
Or you can edit the configurations file in the model_config folder. At the end of the file change the "versionOS" value from 1 to 3.
There is no easier way to make an animation for ...

This is easily possible and simple to implement. But it won't work with the EDITOR alone, a little knowledge of javascript is necessary.

Send me the original image files (before converting them to dials). I will see if there is anything I can do about it.

https://i.postimg.cc/DZ1j9xcT/1721376580804.png

https://i.postimg.cc/KcrpQsz7/IMG-20240719-112533.jpg
Here is a photo of the watch and a screenshot taken on the watch (not in the editor). The photo shows more artefacts than the screenshot. This indicates that the screen cannot display smooth ...

This is possible only if you write the watch face code yourself, and not make it from ready-made elements in the editor. You can't do it in the editor.

@asoo, we have added a Active 2 section on the website. You can now upload your watch faces to the catalog for testing and sharing with others.

Try this
pointer is not an img in the code, it must be treated differently

let colornumber_main = 1
let totalcolors_main = 5
let namecolor_main = ''
let pointerstring = 'pointer_1.png'

function click_ColorStyle() {
if(colornumber_main>=totalcolors_main) {
colornumber_main=1;
}
else ...

Try this
pointer is not an img in the code, it must be treated differently

Changing properties with hmUI.prop.MORE is correct in this case. But I don't understand why to add an additional variable ‘pointerstring’? I would change the function like this

let colornumber_main = 1
let totalcolors ...

I think it's more correct to write to Amazfit support to have them fix this issue.

This may be a temporary solution for now. But you have to decide what is better for you: sometimes showing unknown weather instead of rain or sometimes showing rain instead of unknown weather. Personally, I've only ...