yes it is wifi only ipad The wifi-only iPad doesn't have GPS hardware, so the only location updates you will get are based on nearby WiFi networks. It will not be able to calculate useful speed numbers from that. If you're lucky, you'll find that the reported speed accuracy is < 0, meaning that the speed value is unknown.

triple w dot ime.usp.br/~pf/sedgewick-wayne/algs4 then add GrahamScan dot java at the end of the url. It actually says right at the top of that code: "May be floating-point issues if x- and y-coordinates are not integers." This is exactly the numerical stability issue that I am referring to.

In the image that you linked to in your comment, the orange shape is not convex. Its bottom edge is concave.

it says im posting something that is not permitted You need to spell out some URLs to defeat the filter, i.e. put spaces between the characters to break it up, or replace . with DOT, etc. My goal is to create a convex hull to show the path of a typhoon. Could you post maybe a screenshot from your Android app to show what result you want? I'm a bit confused because I see the path as likely concave, not convex. https://github.com/raywenderlich/swift-algorithm-club/tree/master/Convex%20Hull That's not numerically robust. Are you doing the calculations on the geographic coordinates, or on the screen coordinates?

I am trying out Swift Clipper What are you going to do with the output of the algorithm? Does it need to be numerically robust? In my experience, it's easy to write geometric algorithms but very difficult to write them robustly. Non-robust algorithms will produce outputs with subtle problems that can cause hard to find bugs in the downstream code.

How does the speed that you get compare to sending similar files using AirDrop?

Hi Quinn, you really need to talk to your management about what will make them happy as far as these warnings are concerned. I am seeing a lot of these warnings due to sprintf(), and the problem I have is that the large number of them clog up the "issue navigator" (or whatever it's called). It's easy to overlook other warnings. So what will make "my management" happy would be disabling the warnings, without also losing other deprecation warnings. Can you suggest how to disable these specific warnings? I note that, for example, there is/was a preprocessor macro that could be used to hide OpenGL deprecation warnings. Anything like that for these? Edit: I've just noticed this thread is old. Not sure why it has just popped up. Maybe someone added a post and then deleted it? Hmm.

Do the functions that you enqueue actually run? I could imagine that if you enqueue many functions but they never run, then adding more to the queue could get slow. If you randomly press Pause in the debugger, do you find it often inside that dispatch call? If not, maybe you aren't measuring what you think you're measuring.

I am guessing apple doesn't have an issue regarding this Haha nope. Do you imagine that anyone would use IAP and pay even 15% let alone 30% if they could bypass it by doing that? Read your developer agreement.

I have very little experience with TestFlight so I cannot really comment on what will happen there. In production, the original version reported is the CFBundleVersion from the Info.plist, I believe.

What do you mean by "legit" ? What exactly are you asking?

There does not seem to be a way to remove hosted content from App Store Connect You do have local copies of the content, right? so I'm wondering what the process is for migrating to on-demand resources. There is no automated process.

I would use Apple Design Resources for such a feedback. OK, I've sent it. Let's see if it reaches someone appropriate!

GPCJ is a Java port of Alan Murta's GPC, which is in C. The C GPC code is still available though not from the original site. Calling that C code from Swift should not be difficult. https://github.com/rickbrew/GeneralPolygonClipper But: I only wish to draw the convex hull of the typhoon path in maps Well you don't want a polygon clipper, you want a convex hull algorithm! I would consider using the version in Boost.Geometry (C++), with a suitable wrapper. Beware, it is easy to write a bad convex hull implementation due to the numerical stability issues.

Can I get away with 8GB RAM and 256 GB SSD ? Probably, yes