Made my first watchface with version 0.13.0. and i think i found a bug.
I made a hand with the special new lightning options.
I did set Auto Rotation to ‘SECOND’ and movement set to ‘Quartz’.
It looks good in WFD but not on the watch itself. The movement is ‘Smooth’ there.
With hands without the new lightning option the quartz movement still works fine.
I dont’t know of that’s a WFD issue or a launcher issue.
Made my first watchface with version 0.13.0. and i think i found a bug.
I made a hand with the special new lightning options.
I did set Auto Rotation to ‘SECOND’ and movement set to ‘Quartz’.
It looks good in WFD but not on the watch itself. The movement is ‘Smooth’ there.
With hands without the new lightning option the quartz movement still works fine.
I dont’t know of that’s a WFD issue or a launcher issue.
Your program is great, however, I have a small suggestion that you could add the option to the battery option also the second angle that limits the range of the indicator. I would be very grateful. Regards.
Made my first watchface with version 0.13.0. and i think i found a bug.
I made a hand with the special new lightning options.
I did set Auto Rotation to ‘SECOND’ and movement set to ‘Quartz’.
It looks good in WFD but not on the watch itself. The movement is ‘Smooth’ there.
With hands without the new lightning option the quartz movement still works fine.
I dont’t know of that’s a WFD issue or a launcher issue.
Greetz
Bert
Thanks for the report. I’ll check it out.
It’s a problem on WFD. I’ll soon release a version with it fixed. Thanks.
If have an issue and want to ask you if you can look into it.
Sometimes i use WFD on my work laptop and that one has on old Java version.
Because of the old version i have limited memory.
So if i open a watchface that’s to big i get this error.
ERROR: java.lang.OutOfMemoryError: Java heap space
But the problem is that this error is not shown once, but continuously and seems to be looping.
This makes the program impossible to abort and hangs up my laptop.
Is it possible to make WFD stop after an error and give you the change to save and exit?
(Because it’s my work laptop i can’t update Java myself due to permission rights etc.)
If have an issue and want to ask you if you can look into it.
Sometimes i use WFD on my work laptop and that one has on old Java version.
Because of the old version i have limited memory.
So if i open a watchface that’s to big i get this error.
ERROR: java.lang.OutOfMemoryError: Java heap space
But the problem is that this error is not shown once, but continuously and seems to be looping.
This makes the program impossible to abort and hangs up my laptop.
Is it possible to make WFD stop after an error and give you the change to save and exit?
(Because it’s my work laptop i can’t update Java myself due to permission rights etc.)
If have an issue and want to ask you if you can look into it.
Sometimes i use WFD on my work laptop and that one has on old Java version.
Because of the old version i have limited memory.
So if i open a watchface that’s to big i get this error.
ERROR: java.lang.OutOfMemoryError: Java heap space
But the problem is that this error is not shown once, but continuously and seems to be looping.
This makes the program impossible to abort and hangs up my laptop.
Is it possible to make WFD stop after an error and give you the change to save and exit?
(Because it’s my work laptop i can’t update Java myself due to permission rights etc.)
Greetings
Bert
Ok. I’ll see what I can do about it.
The same thing happens if you have the simulation running and change a setting that calculates on a change like emboss.
Way to reproduce:
1 Add a digital clock
2 Delete any number from a text field and make sure there is no space as in it’s empty, but still checked as text
3. Add emboss to the digital clock later
Sept 11, 2018 20:52:43 GMT 1kensupen said:
The same thing happens if you have the simulation running and change a setting that calculates on a change like emboss.
Way to reproduce:
1 Add a digital clock
2 Delete any number from a text field and make sure there is no space as in it’s empty, but still checked as text
3. Add emboss to the digital clock later
Pop up Java error boxes.
Sorry, this one I couldn’t reproduce. Can you tell me what message it shows on the popups?
Sept 11, 2018 20:52:43 GMT 1kensupen said: The same thing happens if you have the simulation running and change a setting that calculates on a change like emboss.
Way to reproduce:
1 Add a digital clock
2 Delete any number from a text field and make sure there is no space as in it’s empty, but still checked as text
3. Add emboss to the digital clock later
Pop up Java error boxes.
Sorry, this one I couldn't reproduce. Can you tell me what message it shows on the popups?
Nevermind. This seems to be fixed in version 0.13.0. If I find another way to reproduce, I'll post it here.
Wow!, I’ve not been over here since version 0.11.0! Two new releases with lot of amazing features to try! Fantastic job as always Marco!
Well, two things:
When I start 0.13.0 and directly click on PREVIEW BUILDER MODE tab, I get this error…
2018-09-22 21:09:15 [AWT-EventQueue-0] org.marcoferreira.watchfacedesigner.WatchFaceDesigner.uncaughtException()
ERROR: java.lang.IllegalArgumentException: setSelectedIndex: 0 out of bounds
at javax.swing.JComboBox.setSelectedIndex(Unknown Source)
at org.marcoferreira.watchfacedesigner.PreviewViewPanel.setSelectedTemplate(PreviewViewPanel.java:495)
at org.marcoferreira.watchfacedesigner.WatchFaceDesigner.updatePreviewView(WatchFaceDesigner.java:414)
at org.marcoferreira.watchfacedesigner.WatchFaceDesigner.lambda$new$1(WatchFaceDesigner.java:354)
at javax.swing.DefaultSingleSelectionModel.fireStateChanged(Unknown Source)
at javax.swing.DefaultSingleSelectionModel.setSelectedIndex(Unknown Source)
at javax.swing.JTabbedPane.setSelectedIndexImpl(Unknown Source)
at javax.swing.JTabbedPane.setSelectedIndex(Unknown Source)
at javax.swing.plaf.basic.BasicTabbedPaneUI$Handler.mousePressed(Unknown Source)
at javax.swing.plaf.synth.SynthTabbedPaneUI$1.mousePressed(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at javax.swing.JComponent.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$500(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue$4.run(Unknown Source)
at java.awt.EventQueue$4.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
Marco, could you make a video showing new features from releases 12 and 13. It would be great so we don’t lose any fantastic new feature.
By the way, I’m going to update spanish translations to the last release. I have to open the spanish file (translations_es.properties) to make the new translations, right?
Sept 28, 2018 20:03:26 GMT 1kensupen said: Will the animated rotation movements be fixed in the next release along with the new animated digits?
Yes. And the bug you previously indicated (with the "infinite" exceptions) will also be fixed
It's almost ready for release. I just gave it to ricktop so he could test the animated digits in conjunction with Universal Launcher I'll publish it as soon as I have a "working" reply from him
Here you are the spanish translations. I used translations.properties to make translations and this is the translations_es.properties. If there’s any problem with it, let me know.
Bye!
Thanks. They will be included on the next release. But, as usual, I'll also have new strings to translate, so your job if not finished
Wow!, I’ve not been over here since version 0.11.0! Two new releases with lot of amazing features to try! Fantastic job as always Marco!
Well, two things:
When I start 0.13.0 and directly click on PREVIEW BUILDER MODE tab, I get this error…
Marco, could you make a video showing new features from releases 12 and 13. It would be great so we don’t lose any fantastic new feature.
By the way, I’m going to update spanish translations to the last release. I have to open the spanish file (translations_es.properties) to make the new translations, right?
Thanks a lot!
Thanks for the bug report. Fixed it. Next release will work correctly (I hope).
That wont be easy, because it requires time… I’ll try, though.
Here you are the spanish translations. I used translations.properties to make translations and this is the translations_es.properties. If there’s any problem with it, let me know.
Bye!
Thanks. They will be included on the next release. But, as usual, I'll also have new strings to translate, so your job if not finished
Of course!. Sometimes the problem is that without knowing the context, some items are confusing to translate, then if I'm be able to find it in WFD I can check if the translation it's OK or otherwise, make the correct change. But it's funny to do it!.
Here it is, version 0.14.0 of WFD. This one is a major release. It may not have lot’s of new things (it has), but the new things are major differences between what we had. Specially the support for the NEW ANIMATED DIGITS on Eric’s Universal Launcher.
Without further ado, here’s what’s new:
New Create Animated Layer by Changing Text menu option
Corrected movement types on animated layers
New Animation property: Frame display order. Can be normal (1,2,3,4,1,2…), reverse (4,3,2,1,4,3…), bouncing with repeat (1,2,3,4,4,3,2,1,1,2…) or bouncing without repeat (1,2,3,4,3,2,1,2…)
New Movement type: Digital Quartz. The hand skips like quartz but without going through fractional movements.
Fixed Animated Layers export: some frames could have different sizes from other frames. Now they all have the same size.
Added animated digits support on Digital Clock
Added autobackup when running out of memory
Added autobackup when too many exceptions are detected (cascading failure)
Added visual information when a feature that is (probably) not compatible with stock clockskin launcher is used
(internal change) New background rendering thread engine. It should allow for a more fluid UI when previewing watch movements. Please report if something strange happens with the rendering.
Added a splash screen to ease the loading time
New Digital Clock scale method: Fit all Digital Clock inside. This will rescale all the images used in the layer proportionally so that the all the layer fits inside the specified dimensions.
New Flat Tire display
New simultaneous Preview Movements and Preview Fixed Data (previews the watch as if time had just changed to the time on the Fixed Data dialog)
New Digital Indicator to show hours, minutes, seconds, power and steps as a “circular chart”
Fixed preview of hour rotation on some cases to mimic the Finow X5 stock launcher
Drag and Drop on Layers tree
Improved hand movements when rotation multiplier is different of 1 and movement type is not SMOOTH. Now it still moves on small steps, but at a different speed.
Application icon is now displayed correctly on Mac OS X