Open mickeyl opened 11 years ago
Found same issue with the example.
Have you found a solution to the issue?
I have submitted a bug against iOS and Apple has requested me to add some StackShots, which I'm going to provide. No app should be able to do such a fatal operation, so I guess the creator of SDSegmentedControl is waiting for Apple to fix it.
So really this is unusable at this point?
Yes, for this particular combination (arrowSize = 0.0 and adding segments at runtime). I did not manage to get the StackShots yet for Apple, but i'm working on it.
SDSegmentedControl manages to hard-freeze iOS (6.x), so that only a forced shutdown makes it work again. I have created a minimal example that puts the blame on a combination of arrowSize = 0.0 and adding segments at runtime. My theory is that one of the UIKit and/or CoreGraphics library functions is called with an excessive parameter (CGFLOAT_MAX anywhere?) that makes the graphics card go havoc. Here is the minimal example. Note that the simulator handles this case without problems, just the devices (tested on multiple phones and pods) hard-freeze.