Jan 7, 2018 12:17:53 GMT 1gabolander said: Marco, do you have some sort of value/strings.xml or .mo or something in your WFD java project, so I could create italian localization for the program in my very spare time?
yes, I do. It may not be complete, but it is, for sure, almost complete. However it was an automatic extract so some keys/values may seem strange, but do use them.
I’ve attached to this post the original (english) translation. Just rename the file to translation_it.xml and translate it. One you send it back to me, I’ll include it on newer versions.
Jan 7, 2018 7:34:48 GMT 1druss1981 said: How can I permanently change the frame rate of a gif? if I change the frame rate in the watchfacedesigner it will not be taken over in the finished watchface on my watch.
You are right. It seems to be an issue on Universal Launcher. I'll try to check it with ricktop...
Right, framerate was not working, next update 2.5 will correct the issue.
Bug (or strange behaviour at least): RECTANGULAR LAYER: When setting HEIGHT to <= 2.2, it draws a point, no matter what value in WIDTH. This situation, in WFD early versions, drew a line. I usually do this to make lines, markers or whatever you want to call it, to help me aligning objects, mainly hands.
However if you change the values, I mean WIDTH <= 2.2 and HEIGHT any (high) value, it draws a line, in last version, what is the right behavior I think
So please Marco if you can take a look at it I would be very grateful.
Started it with ‘java -jar WatchFaceDesigner.jar’ and this is the output:
Restarting to increase memory
Invalid maximum heap size: -Xmx16g
The specified size exceeds the maximum representable size.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Instance started with max memory set
jan 08, 2018 7:53:58 PM java.util.prefs.WindowsPreferences
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(…) returned error code 5.
Rendering Rectangle took 64 ms
I have 16Gb Ram installed on my PC
Bert
Hi,
from what I could figure out, you have the 32-bit version of java installed. You can check it by running “java -version” on the command-line. The 64-bit version outputs something like this:
java version “1.8.0_151”
Java™ SE Runtime Environment (build 1.8.0_151-b12)
Java HotSpot™ 64-Bit Server VM (build 25.151-b12, mixed mode)
(emphasis mine).
If you have the 32-bit version, you’ll never be able to use much of your RAM. I’d advise you to install a 64-bit version instead (or you can have both at the same time, but in that case you should put the 64-bit version on path before the 32-bit version).
Anyway, even with 32-bit java, try running “java -Xmx1500m -jar WatchFaceDesigner.jar has_xmx” and it should give you a value closer to 1,5Gb. You can try higher values, but the maximum amount is limited by the 32-bit architecture…
The more ram available to WFD, the faster it will run…
You can download java at java.com. If your browser is also 32-bit, it will automatically recommend the 32-bit version. Just select “All java downloads” and a 64-bit version will be available there for sure.
Bug (or strange behaviour at least): RECTANGULAR LAYER: When setting HEIGHT to <= 2.2, it draws a point, no matter what value in WIDTH. This situation, in WFD early versions, drew a line. I usually do this to make lines, markers or whatever you want to call it, to help me aligning objects, mainly hands.
However if you change the values, I mean WIDTH <= 2.2 and HEIGHT any (high) value, it draws a line, in last version, what is the right behavior I think
So please Marco if you can take a look at it I would be very grateful.
I attach examples of both situations…
Thank you for the bug report. I’ve just fixed it. I’ll release the fixed version in 5… 4… 3… 2…
Here is a small incremental release. It is mainly a bug fix with a new feature added: Lens effect. This effect will distort the layer it’s applied to in order to (badly) simulate a fish-eye view… Since a picture is worth more than a thousand words, here is a gif (it seems to be trendy right now ) showing the effect. The same font is used for the seconds and the hours/minutes. But a lens effect has been applied to the background and to the seconds digital clock layer…
Jan 7, 2018 12:17:53 GMT 1gabolander said: Marco, do you have some sort of value/strings.xml or .mo or something in your WFD java project, so I could create italian localization for the program in my very spare time?
yes, I do. It may not be complete, but it is, for sure, almost complete. However it was an automatic extract so some keys/values may seem strange, but do use them.
I’ve attached to this post the original (english) translation. Just rename the file to translation_it.xml and translate it. One you send it back to me, I’ll include it on newer versions.
Oh well ... Honestly, I must admit that maybe at almost 50 yo I realized to know better english than my motherlanguage (italian, indeed!) LOL 😂😂
… just kidding, but banding jokes … I explain what I mean: as often happens, in different sentences some english words may have more meanings and translations in italian, depending on the context where they appear.
For this reason, I have to check my translations in the different part of the application, if they can stay or if they are really ugly.
So I ask you to try to apply my translation’s xml that I’ve already done, attached here, and share me somewhere your temporary application version, so I can take a look to all the program and check if the jobs is correct, before publishing it definitively.
Keep present the following things:
I dunno if single quotes on descriptions (') are good or may give issues and have to be escaped (eg., \').
I dunno if accented letters (several in italian language) have to be escaped or localized in utf-8 in your apps. Eventually they could be converted in their corresponding html code for HTML parts (eg., è for è, etc.)
Note for you: I realized that CREATE_DIGITAL_CLOCK_LAYER and CREATE_CHARGING_ICON_LAYER entries, have the same title and description in original translation file (maybe for a copy&paste and a tweak missing.. may happen  ). I already corrected (I think) the italian side.
Note for you: I didn't find any entries in the original file, for customizing the entries for the SELECT adaptors of the programs, such as "ALWAYS, INVERT_BOTTOM, LINEAR GRADIENT, HOUR_24, TEXTURE, etc.. Are they fixed string as of now, or missing somewhere else? Or simply is this the part you talked about, when you said "It may not be complete"? Need to know, because if they have to stays as is, I need to change some italian descriptions too accordingly, at least where they refer to those options..
Anyway, I can manage and reorganize italian translation each time you release a new application version. I give all my support for it as far as my possible…
At the moment, no more things come to my mind to tell you.
I look forward to hearing from you soon.
Best,
Gabo
EDIT: Sorry, filename was bad, I corrected and re-uploaded here: translation_it.xml (22.56 KB)
Bug (or strange behaviour at least): RECTANGULAR LAYER: When setting HEIGHT to <= 2.2, it draws a point, no matter what value in WIDTH. This situation, in WFD early versions, drew a line. I usually do this to make lines, markers or whatever you want to call it, to help me aligning objects, mainly hands.
However if you change the values, I mean WIDTH <= 2.2 and HEIGHT any (high) value, it draws a line, in last version, what is the right behavior I think
So please Marco if you can take a look at it I would be very grateful.
I attach examples of both situations…
Thank you for the bug report. I’ve just fixed it. I’ll release the fixed version in 5… 4… 3… 2…
Bug fixed! Great. Thanks a lot. That’s very useful to me.
Jan 9, 2018 15:24:17 GMT 1gabolander said: Oh well ... Honestly, I must admit that maybe at almost 50 yo I realized to know better english than my motherlanguage (italian, indeed!) LOL 😂😂
… just kidding, but banding jokes … I explain what I mean: as often happens, in different sentences some english words may have more meanings and translations in italian, depending on the context where they appear.
For this reason, I have to check my translations in the different part of the application, if they can stay or if they are really ugly.
So I ask you to try to apply my translation’s xml that I’ve already done, attached here, and share me somewhere your temporary application version, so I can take a look to all the program and check if the jobs is correct, before publishing it definitively.
Keep present the following things:
I dunno if single quotes on descriptions (') are good or may give issues and have to be escaped (eg., \').
I dunno if accented letters (several in italian language) have to be escaped or localized in utf-8 in your apps. Eventually they could be converted in their corresponding html code for HTML parts (eg., è for è, etc.)
Note for you: I realized that CREATE_DIGITAL_CLOCK_LAYER and CREATE_CHARGING_ICON_LAYER entries, have the same title and description in original translation file (maybe for a copy&paste and a tweak missing.. may happen  ). I already corrected (I think) the italian side.
Note for you: I didn't find any entries in the original file, for customizing the entries for the SELECT adaptors of the programs, such as "ALWAYS, INVERT_BOTTOM, LINEAR GRADIENT, HOUR_24, TEXTURE, etc.. Are they fixed string as of now, or missing somewhere else? Or simply is this the part you talked about, when you said "It may not be complete"? Need to know, because if they have to stays as is, I need to change some italian descriptions too accordingly, at least where they refer to those options..
Anyway, I can manage and reorganize italian translation each time you release a new application version. I give all my support for it as far as my possible...
At the moment, no more things come to my mind to tell you.
I look forward to hearing from you soon.
Best,
Gabo
EDIT: Sorry, filename was bad, I corrected and re-uploaded here:
Thank you for your efforts. I’ve been making changes to make it easier for you (and all those who wish to translate this app) to translate and verify the results. The next release will include the translations files on a sub-folder of WFD. That sub-folder will also include a small utility I just wrote to help see what’s translated and what’s not translated. Also, using this utility, you wont have to worry about special chars, as they will be taken care automatically. Also, as soon as you re-run WFD, it will use the translation corresponding to your system (from that folder). I’m just giving it the finishing touches. It’s also 3:35 AM in here and I must go to sleep, otherwise tomorrow (in a few hours) I wont be very productive at work .
Those items you said are missing, are still missing. Yes, those are a few of the “unfinished” parts on the translation support. As soon as you detect them, just send me a warning so that I don’t forget about them, please
Jan 10, 2018 4:40:00 GMT 1mpmf said: Thank you for your efforts. I've been making changes to make it easier for you (and all those who wish to translate this app) to translate and verify the results. The next release will include the translations files on a sub-folder of WFD. That sub-folder will also include a small utility I just wrote to help see what's translated and what's not translated. Also, using this utility, you wont have to worry about special chars, as they will be taken care automatically. Also, as soon as you re-run WFD, it will use the translation corresponding to your system (from that folder). I'm just giving it the finishing touches. It's also 3:35 AM in here and I must go to sleep, otherwise tomorrow (in a few hours) I wont be very productive at work .
Those items you said are missing, are still missing. Yes, those are a few of the “unfinished” parts on the translation support. As soon as you detect them, just send me a warning so that I don’t forget about them, please
Ok, thank you Marco, you have been clear at all, and congrats, you are keeping on a very great job.
I wait for your WFD version with translations support, so it’s easier for me (for us) to detect the untranslated parts and to verify my translaction activity before releasing it to you.
At 3:35 AM you’d better go to sleep but “I preach good but scratch badly”, because I often do the same and I’m totally stunned the day after at work …
This release is, feature-wise, a very small release. However, it is a big change in the multiple-language support mechanism. WFD can now read “external” (in the translations folder) files at bootup, select the one according to the system language and use it to show the textual information. This makes it easier to create/change new translations, since with a simple re-run, one can see the effects of the changes in the translation file. To simplify the translation work, I’ve also developed a tool that shows the original and all the available translations of a selected properties file. The user can then easily see what’s already translated and what’s needed to be translated (red background) and can change the text of any translation. Here’s a screenshot:
There was one new feature, however. The Glow Effect now has a “tolerance” slider, that allows to set a tolerance to the threshold of brightness. What it does is making the pixels not has bright as the threshold but still within the tolerance to glow with lower intensity (glow more when the pixel brightness is near the threshold, glow less when the pixel brightness is further away from the threshold).
This is the Glow Effect with Tolerance 0 (as was in previous versions). The Glow Effect is applied to the outer blue circle surrounding the Earth (filled with a linear color transition from bright blue to black).
This is the Glow Effect with Tolerance 0.05. Notice as the glow is now not stopping abruptly, but continuing fading as the brightness of the layer decreases.
I wait for your WFD version with translations support, so it’s easier for me (for us) to detect the untranslated parts and to verify my translaction activity before releasing it to you.
At 3:35 AM you’d better go to sleep but “I preach good but scratch badly”, because I often do the same and I’m totally stunned the day after at work …
Read you soon.
Greetings
Gabo
I’ve just released the promised version. I’m sure there are still some strings left to internationalize, so if you find them, please don’t hesitate in telling me so I can fix them.
I wait for your WFD version with translations support, so it’s easier for me (for us) to detect the untranslated parts and to verify my translaction activity before releasing it to you.
At 3:35 AM you’d better go to sleep but “I preach good but scratch badly”, because I often do the same and I’m totally stunned the day after at work …
Read you soon.
Greetings
Gabo
I’ve just released the promised version. I’m sure there are still some strings left to internationalize, so if you find them, please don’t hesitate in telling me so I can fix them.
Thanks for your translation.
Sure, you can count on it, Marco.
Thanks for keeping on the good work.
Does your tool cover all the clockskinmaker tool options?
Does your tool support second region time? (I want to add for example gmt time or london time with second hour hand)
Does your tool supoort chronograph functionality?
Thx
Ronen
Hi,
I don’t think it covers all of the CSM tool. It does cover the most used use cases, but I consider CSM the goto tool when wanting to go into low-level (in the guts) fine-tuning.
It’s not that my tool doesn’t support it, but the clockskin engine on android watches does not support it! If/when the clockskin start to support it, so will my tool.
I’ve read all topic but missed answer for two questions:
what is a difference between SECOND and SECOND_SHADOW in autorotation?
how to adjust ticks for second hand instead of smooth move?
Thank you, wicy.
The _SHADOW rotations behave a bit like shadows would. That is, they are not rotated exactly to where the second is, but are a little below of the seconds handle. As an image speaks more than a thousand words, here is an example. The Blue handlle has second_shadow in autorotation. The white hand has second in autorotation…
The clockskin engine on the watch does not support that kind of rotation, so I can’t force it to on the designer…
Jan 11, 2018 21:14:46 GMT 1gabolander said: Hi Marco, I gave my humble contribution to support your efforts for the great work of Watchface Designer project.
Trn ID: 96027107GN9905603
I’ll be back to you as I’ll have completed and looked after italian translation.
Have a nice time, looking forward…
Best,
Gabriele
Thank you for your support, it's very appreciated. I'll add your name on the donors list on the about box of WFD.
Jan 11, 2018 23:50:48 GMT 1mpmf said: Thank you for your support, it's very appreciated. I'll add your name on the donors list on the about box of WFD.
You are welcome, Marco, and thank you for adding me in the donors list.. :-)
Let’s go speaking back to translations now…
I completed italian translations and verified along the program and I feel it looks good for now for the latest version of WFD. I leave you here: translations_it.properties (22.68 KB)
Currently, I found some untranslated words/entries for:
All selectors of watch preview window, as highlighted here:
In some description like "Fill Style/Color", "Stroke Style/Color" (but only for Style and Color words) and some selector of the object/layers control windows, as highlighted here:
