The new Edge Complication (both Duo and Quadrant) are very cool EXCEPT after lots of work making it look like I want, it (Duo this time) doesn’t appear on the Pixel 3.
I am wondering if it could be happening because I haven’t moved to Wear OS 5.1 yet. I keep thinking that update will arrive soon. No, tapping doesn’t bring it down. I guess I have to wait for Google.
I re-categorised your Topic . I hope you get some response asoon . I wonder in the light of your Other experience a Reboot of watch and PC would help . I note that the reported Memory usage in Properties in the Faces Folder only updates after the second load and save . The Extra stuff does no get deleted first save . I a not talking about the Memory usage Plugin . I am talking about the Microsoft Windows File properties .
Hi - tried uninstalling and reinstalling 1.8.7. I’ve also rebooted the Watch. That did not solve the issue of the Duo Edge complications not showing up on the Pixel Watch 3. All the other elements appear properly on the watch. Only those new complications do not. The same issue occurs with the Quad Edge complications.
I’m all out of bright ideas. Anyone else?
No sorry . I feel ike I am bashing my head against a brick wall . The responders are saying that the engineers are looking at the Issues . But when a solution will be is any body’s guess .
Hey @Purrstachio2Cat ,
I’ve tried to reproduce this issue on watch ultra (WearOS 5.0) and it is working fine, but I did not customize it much. It would be helpful if you provide your wfs file.
Thanks - the problem seems to be limited to the Pixel Watch 3 - at the moment it’s Wear OS 5, but the 5.1 update should show up soon. Not sure if you can open it on a Watch Ultra.
New Complications.zip (1.4 MB)
Oddly, it works great on the WFS editor - just not when loaded on the watch. All the elements show up nicely (on the watch) except for the Edge Complications.
How are you manipulating the Edge complications? They are completely locked when I add them to my project. Dimension, placement, size and placement of the elements inside the complications, are all locked. It pretty much makes the whole thing useless. I can’t even change the Font Size for Text Elements.
I can do all sorts of things on those edge complications on the WFS editor screen, but then absolutely nothing shows up on the Run Screen (maybe 1) and nothing at all on the watch (Pixel Watch 3).
So your size, placement, font size, etc are not grayed out?
Oh yes, I see where you’re going with your question. When I said I can do lots of things, I meant colors and fonts. Many of the other options (placement, angle, dimensions, font size, and such) are grayed out. They need to be so that those complications stay exactly where they are supposed to be. Having built those by hand in 1.7.13, I can tell you it only takes a tiny bit of movement (like a pixel or two) to mess up the whole design and forever to fix it. My problem, as I said, is that I can do things in the editor, but very little shows up on the Run screen and even less on the watch. I’ve given up and returned to 1.7.13.
Apparently, folks in the Apple world are getting this update to work. Perhaps someday they will take pity on those of us using Windows and provide a working update for these cool complications.
Thanks for the feedback. I’ll never use them, because of this. They should make it so you can unlock them. I can’t deal with the very tiny font size they chose.
The other thing they need to do is make it so we can apply color theme at the complication level, instead of having to go into EVERY individual element within the complication…and make it so when you duplicate something, we don’t have to go remove the word “copy” in every single element to get it to look nice in WFS.
It’s a particular look. If you don’t like it, you don’t have to use it. Here’s the one I built by hand in 1.7.13. You’re welcome to play with it if you like.
"C:\Users\mtrem\OneDrive\Desktop\WthrPlus_Duo Bars1.zip
Link is not Active . I usually just add .ZIP to the end of the file name . Most are familiar with just deleting that to open it in WFS .
I tried that - it wouldn’t let me send it even though .zip is supposed to be usable extension.
So, it should be WthrPlus_Duo Bars1.wfs.zip? I don’t think I’ve had much luck with that one either.
I just built two by hand, actually one, refined it, and then copied it. It took about an hour, and it does everything, and doesn’t get wonky when I manipulate the fonts and stuff. I just never tried it before. So I guess in a sense the new enhancements got me to try something new.
Yes exactly but I am not sure why it is not highlighted .
Good for you. Never know what you can accomplish until you try. Congrats.
This is what I upload . From my folder where I have a few Fake .ZIP Files . Isee you uploaded one earlier in the topic .
.
BIG_HEART_TEST.wfs.ZIP (209.6 KB)
.
.
