Post not yet marked as solved
Well after a wee dram of Grand Marnier, I think I got this figured out. There are CATransform3D structures that have a m34 property and the trick was to set that to an appropriate value that controls how much 'tilt' there is in the text. You also have to apply a CATransform3DRotate to the text. Then in a text view layer, apply the transform to the layer that contains your text.
Whew!
I'll try and strip the code down to something small and post it here (for posterity ;-))
John
For me, Xcode (Version 12.3 (12C33)) was beach-balling every 5 minutes as well. I just turned off 'Connect Via Network' for my one physical device - an iPhone X (14.3 18C66) and that seemed to return Xcode to 'normal'! Now if I could just get rid of those @#$%^ "watchdogd checkin" crashes...
Post not yet marked as solved
Hi Claude:A little test harness I bashed together kinda works. Problem is that any items around a button I'm animating moves. If you check out the Watch unlock or Calculator, the resized buttons are 'over' the button beneath it. And there's the bit that a number in the corner like 7 or nine expand into the center; where 5 zooms up in all directions. I'm going to play around with UIGraphics and friends and see what I can see.Any constructive ideas are appreciated.John
Post not yet marked as solved
Quinn:Yeah, it's my test. In an ill-advised ;-) attempt at getting 'super accurate' results, I dragged out my old Quadra 840AV (amazed that it still booted and the good old days of Mac OS 8.1), installed my old copy of Mathematica and told it to give me some constants accurate to something silly - 100 decimal places. One of which was Pi. I used the Mathematica constant in my app and that's when I noticed the error. So if I use pi to 20 decimal places - 3.14159265358979323846 - all is good.Thanks for your time and patience.John
Post not yet marked as solved
Thanks Quinn. Sorry about being vague, I understand that completely. I should have provided more info.But shouldn't the first result be 6.3661977^49? It's in the range of what an NSDecimal can handle and that's the answer my beatup-old HP-25C says.John
Post not yet marked as solved
Claude:Sorry about the compile errors, I thought I had just copied the code out of Xcode and pasted it in here. I know about the range of an NSDecimal. Looks like a serious debugging session this weekend. 😉.ThanksJohn
Post not yet marked as solved
Thanks Quinn!Will do that today.John
Post not yet marked as solved
Thanks Claude.I originally was using doubles (actually double_ts), but found that those didn't quite work with the requirements. NSDecimalNumbers helped alot, except for the 'change' problem.I think that I'm not correctly setting up the NSDecimalHandler properly to handle the rounding.I was originally going to whip up a couple of test harnesses to see if I can get a handler that meets the requirements.Have a good dayJohn
