FintasticMan

The calculation hasn't changed since we improved it in 1.12. When we did that, we made sure to err on the side of caution, so the percentage might be slightly...

I have my suspicions that it's due to the compile-time apps, as that was the only time we've changed ApplicationList recently.

About the printing of the value, I think that doing something like what's done here should be fine: https://github.com/InfiniTimeOrg/InfiniTime/blob/361e381ac32ff7a05abeaaf1e85eb10818193f64/src/displayapp/screens/BatteryInfo.cpp#L38 Edit: looking at the code, seems like you're already using something...

You can either leave the format string as `"%ld"`, or you can use [fixed width format literals](https://en.cppreference.com/w/cpp/types/integer#Format_macro_constants). This would mean that the format string would become `"%" PRId64`. To use...

Looks good, I've tried this on my watch and it works quite nicely. I do think that it is better to use floats rather than doubles for the pow calculation....

> I thought that double matches the 64-bit integers better than float. Is that correct? :thinking: While doubles are 64 bits wide, that doesn't make a difference for int >...

I think this is similar to #1461, right? I think this is a very useful feature, let's decide on a good implementation together. It might be good if you could...

This is also an issue with the Infinineat and Casio watch faces, but in those cases it doesn't crash, just doesn't load the resources.

Yeah, I can't see any reason why it should fail... I'll try re-running the workflow. Edit: re-running hasn't seemed to help. Very strange that it's only that workflow that fails,...

Git bisect says the bug was introduced in 39bc166e549e8ccae75468aa2dd3613d51f54e27. There was no call to SetAppMenu removed in that commit... Why didn't the bug occur before?