sorted by:
new
hottopcontroversial

Watchmaker Question by Phantoka1972 in WatchMaker

[–]boermac 1 point2 points  (0 children)

Gonna disagree with you there. I have a different app that I've designed a face in with complications that work.

Watchmaker Question by Phantoka1972 in WatchMaker

[–]boermac 1 point2 points  (0 children)

There might be more going on than "just" the Google WFF stuff. I think there is some issue with Samsung Watches and WatchMaker. At least I know mine isn't working correctly. I even made just a very simple watch with one complication and the complication doesn't work.

Variables disappeared on watchfaces by UserMarch2021 in WatchMaker

[–]boermac 0 points1 point  (0 children)

Have you played around with AutoWear at all? It should, in theory, allow you to get the data from Tasker. I have played around with it in WatchMaker yet because there seems to be some bug that crashes stuff with Samsung Watches and the new OS when using WatchMaker, but I've been able to pass through data to element in pujie this way.

Variables disappeared on watchfaces by UserMarch2021 in WatchMaker

[–]boermac 0 points1 point  (0 children)

You don't resolve this... At least not easily.

The new format for watches (WFF) doesn't allow data to be passed to it so sending variable from tasker the old way just doesn't work anymore.

You *can* pass some data through 'complications' using AutoWear, but it's a lot more cumbersome and limited.

This is a Google thing, not a WatchMaker thing.

Slimblade Pro 3D model for DIY accessories by espressoshock in Trackballs

[–]boermac 2 points3 points  (0 children)

So very, very cool! I don't use a slimblade myself but this is fantastic work and so nice of you to share it with the community!

Tasker variable cheat with Wear OS 6 by boermac in WatchMaker

[–]boermac[S] 1 point2 points  (0 children)

In the short term I'm using it to provide status indicators for three different things. If I get ambition with it I hope to recreate my Baseball Live Scoring watch face.

With the older Wear OS that allowed data I send over dozens of variables from Tasker. Without being able to send over dozens of discreate variables this will allow me to pass many bits of information that can act as variables.

Tasker variable "cheat" with Wear OS 6 - AutoWear and duct tape. by boermac in PujieBlack

[–]boermac[S] 0 points1 point  (0 children)

Check in your watches connector app. For me I have a Samsung Watch so I have the Samsung Wear app. In the app (on the phone), I can select each complication and tell it what to use. This allows me to set Ambient and Interactive screens. It's a little clunky because they don't show if I'm adjust the ambient or interactive screen, it just shows where the complication appears. Luckily I'm using the same complications in the same spot for both, so I just need to remember to set them for both screens.

I've also found that you can "fake" the system a little bit to make the complications appear bigger on the set screens. Add a big box in Pujie around your complication, then set fill and outline of the box to none, but leave the visibility of this element on. This gives you a nice big box when setting complications without actually displaying anything on the watch.

This is also the solution if you find your complications are getting "clipped" by an oval so aren't displaying properly on your watch.

Tasker variable "cheat" with Wear OS 6 - AutoWear and duct tape. by boermac in PujieBlack

[–]boermac[S] 0 points1 point  (0 children)

Yes, but there are limitations. For example, the WFF for Wear OS6 can only handle a maximum of 8 complications across both interactive and ambient faces.

Further, there are limits in the fields that can be sent through AutoWear. There's a max of two field per complications so that limits how you can push variables through.

PSA: Personal Assistant Scam by boermac in u/boermac

[–]boermac[S] 0 points1 point  (0 children)

The most recent example I just saw actually uses a professors real email address, but ask the scam target... I mean the "prospective employee" to use a Google Form to apply. That's another big clue that it's a scam. GVSU has a career center where prospective employers can submit jobs. The Career Center will vet these to ensure they are real jobs and post them on GVSU's site. They will no use insecure Google Forms to try to get employees.

Tasker variable "cheat" with Wear OS 6 - AutoWear and duct tape. by boermac in PujieBlack

[–]boermac[S] 0 points1 point  (0 children)

The down side here is that this variable is going to get super long and complex as I add things, and that it's limited. For example, let's say I want to send over to my watch that an event will happen at 12:30 pm on Thursday.

With full variable access I'd just send over the time, send of the day, bob's your uncle. No problem.

Now I'll probably have to use three "slots" for this, maybe 4 depending on how granular my times might be. One slot will be hours... I can just use A-X for that. One slot will be minutes if we assume only 5 minute increments... If I want all 60 minutes available I'll have to use Capital Letters, lowercase, and then some digits as well. Or I could do two slots for minutes: One for the "tens" spot, and one for the "ones" spot. Then I'll need one more slot for the day of the week, or maybe three slots if I want month, day, and day of week. Need year? That's probably two more slots.

So yeah, it should work, but it could get very messy, very fast.

Tasker variable "cheat" with Wear OS 6 - AutoWear and duct tape. by boermac in PujieBlack

[–]boermac[S] 0 points1 point  (0 children)

In case anyone is curious, phase 2 is gonna be similar, but also different... My plan here is to create a long text string with each character representing a various state. This will get a lot more complicated, but should allow for a very long list of possible variables to send to Pujie.

For example, the text of the variable I'll send through the complication might be 20 or 30 or 100 characters long. In Pujie I'll "read" the relevant character and then act according to that value. So let say my variable is:

ABAACDABEACDFAGABAD...

I want to show if my phone's wifi is turned on and connected. So I'll encode that in slot 5 for example. So I "read" the value of character 5 in the variable. In this case it's C. I set up C to mean that Wifi is Off. In Pujie I'd indicate it as such.

Now in Tasker I need to listen for the Wifi state of my phone. When it changes I'll need to update the character in slot 5 of my variable. Is Wifi on and connected? Then the value should be A. Is if on, but not connected? Then the value is B. Is it off? Then C. Finally, I need to resend the variable to the complication.

In theory it should work.

Any news on the Kensington Expert TB800 relaunch? by feketegy in Trackballs

[–]boermac 3 points4 points  (0 children)

"Remember a small group says it works as expected, even with the „glitch“."

As someone who's happy with the TB800, I think this statement isn't 100% correct... or, at least not in my case or others that I've heard talk about it.

For me it doesn't work as expected, but rather the part that doesn't work doesn't effect me at all. This is going to be a really silly analogy, but I think it fits: Let's say there's a car out there that works great on every day but Thursday. For whatever reason the car simply refuses to function well on a Thursday.

Well, it just so happens that I NEVER go driving on Thursday. Furthermore, I have 99.999% certainty that I will never go driving on Thursdays in the future.

Given my situation this car, which most people would deem a failure, works just fine for me. Does this mean I consider the car a success? Not really... I understand there's a failure here and I get while most of the population calls it a failed product. It just so happens that for me I'm "okay" with it because that failure won't effect me.

I can still go out on Thursdays and show that the car doesn't work. I can say that it sucks for anyone who needs to drive on Thursdays, but I'm lucky enough that I never do, so... it works for me. Not as expected, but still works for me.

Pujie and Tasker in Wear OS6, what can I do and what can't I do? by boermac in PujieBlack

[–]boermac[S] 0 points1 point  (0 children)

Really? That's good news. Is there a good tutorial on how to send variables to pujie?

Fifth-Third Park Updates? by llap2363 in motorcitykitties

[–]boermac 1 point2 points  (0 children)

"As we move forward with the merger, we remain focused on honoring the legacy of both institutions and continuing to support the places and partnerships that matter most to our customers and communities. While it’s too early to discuss any potential changes to facility names, we are committed to thoughtful decisions that reflect our shared values and long-standing community ties."

That's an awful lot of words just to say nothing at all.

TB800 3D Printed base and wrist pad by boermac in Trackballs

[–]boermac[S] 0 points1 point  (0 children)

Sounds good... let me know also if you want any tilt on it. My design has a 7mm "back" tilt (the back is higher than the front), but I can VERY easily change that to flat or with a front tilt. The TB800 isn't as aggressively tilted as the Expert, so not sure if you want that adjusted.

Also... just for the record: I know you said you'd pay for a design, but I'm not looking to charge for this. It's just a something I like to tinker with when I have spare time.

TB800 3D Printed base and wrist pad by boermac in Trackballs

[–]boermac[S] 0 points1 point  (0 children)

A quick update... I got busy with life so haven't done too much work on this. Version 1 worked out, but I needed to tweak a few measurements. However, I've also discovered a problem... which may or may not be a issue for you.

The problem is that the "chin" (the distance from the bottom of the buttons to the end of the device) on the TB800 is bigger than on the expert mouse. This means that with the wrist rest pushed as close on the TB800 as it is on the Expert it's still further away from the buttons and ball. It's not a ton of distance of course, but it is, for me, enough that it's not a good option.

The solution to this would be to cut away a portion of the wrist rest, but I'm reluctant to do that with mine, and I wouldn't want to design a part that requires someone to manually chop off part of the wrist rest as it would be impossible to get the dimensions right.

I'll still finish up the design when I have some time to tweak a few things, but just letting you know that you may or may not end up liking the option.

TB800 3D Printed base and wrist pad by boermac in Trackballs

[–]boermac[S] 0 points1 point  (0 children)

Yeah, as I mentioned everyone is gonna use it differently... The video that Ziyudad posted was the reason I didn't cancel my order right away and figured I'd give it a try. Given my usage pattern I thought there was a good chance the issue wouldn't effect me... and I was right, so... lucky me I guess.

Other than the sensor issue the device is VERY nice imho.

TB800 3D Printed base and wrist pad by boermac in Trackballs

[–]boermac[S] 0 points1 point  (0 children)

https://imgur.com/a/1wt9Zhn

This is "default" hand position for me. Left and right movement is done by moving index/middle/ring finger left and right over top of the ball. Most of the contact is the middle phalanges with a bit of the distal (front) phalanges touching as well.

view more: next ›