Hate to do this, but I feel responsible since I started it. The abort is still happening. Yesterday I was holding down the Q key since it would keep the emulator running, and it would keep going for much longer after I let the key up. Type ahead must have caused it to keep running and I assumed the BIOS update must have fixed it. Not using the Q trick today and it’s aborting as before.
1 Like
FYI, not related to the emulator aborting but regarding watch faces. You can use “tap” or what one might call “flick”. The wrist “flicks” over then up again quickly. This is intercepted in the SDK as a “tap”. You might consider telling Claude to utilize a tap instead of a button. That might replace the functionality of 1 button. The other two might be a design decision.
And also, make sure you are using Claude Code. It’s better for programming type questions.
2 Likes
Thanks, appreciate all the suggestions I can get. I have considered the wrist flick option. At this point I’m waiting for touchscreen support in the SDK as I really want more than the apparent binary operation of the flick.
On the coding front I’ve created a design app with Claude that let’s me specify and tweak a wide range of face elements and options that’s been a huge benefit and time saver, so that I don’t need to get Claude to recode just to change a color, or font size, or the exact position of elements. I can go through any number of iterations tweaking a face bit by bit without using Claude at all. Also have a Save option that creates a file of all the designated parameters and a screenshot so I can review and load a previous design and make changes as desired. I have over 90 saved so far. But I’ll definitely look at Claude Code as well and see what advantages it can provide.
Thanks again.
2 Likes