I ran into a very strange case where if I used this control in an archived ipa sent over testflight, the indicatorYOffset when using HMSegmentedControlSelectionLocationUp would be below the frame where it was supposed to be. (Strangely enough it worked fine when attached and debugging with XCode)
Once I set this to 0 by default I no longer had the issue. I'm assuming it has to do with the fact that inititalized floats may not have to be zero'd or perhaps because I used a xib. Either way, very strange.
set yOffset to 0.0f instead of uninitialized.
Merged, thanks! 😃
I distinctly remember in my C programming course in second year a student arguing that all vars are initialized to 0s and the prof telling him that depending on your implementation of C, it can vary. I can't tell though because in debug mode it worked fine!