Re-post from FaceBook
Kelly Schrock
21 hrs
1.3.5: The "Arm OK, you OK?" release.
When you first start building an app, it's like framing up a building. In 2 days, you go from a hole in the ground to a frame that looks like a building. By the time you get to the point where you're putting light switches and stuff in, progress slows somewhat. I'm currently building something "big" (probably the biggest feature so far) into Solex, but at the same time, taking care of issues people find while you're using the current version. So this update is to address some stuff you've found. Those things are:
. Fix maddening "Arm OK" message
Solex should no longer be chattering about "Arm OK".
. Add pref for gimbal touch control
Someone asked for the ability to make the gimbal pitch on the HUD view proportional, that is, not tied to the "Y" position of your finger on the screen when you swipe. So there's now a "Gimbal Relative Pitch" setting in App settings for that. Turn that on, and swiping considers the *current* "Y" position to be the top. It makes it a little easier to swipe the gimbal up. I'm undecided on which I like better, which is why I made it an option.
:-D
. Fix for TapToFly triggering on accident
It was possible for TapToFly to trigger after you'd dismissed it, which is annoying. That's fixed.
Final thing is the "unresponsive buttons" issue people have been mentioning. I put some logic in the app to monitor its own CPU usage and log it, and did a lot of testing this afternoon. The peak CPU usage I saw was 45% for a 5-second period, when the map view was loading. That's actually pretty good. That's also on a quad-core tablet, so it might appear higher on tablets with fewer CPUs. At one point, I saw a brief spike to 75% when I shut the Solo off and DroneKit pinged the wifi connection for several seconds. But that dropped off, and I wasn't able to reproduce it. I AM looking for this issue, and as soon as I'm able to reproduce it, I'll fix it and push another update.
It's "date night", I'm outta here.
:-D