Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Smaller adjustments will never make the mapview zoom level change. When you pass a region, the mapview decides on what zoom level to use for the best fit. It will never use an "in-between" level. The reason is that the "in-between" zoom levels look fuzzy. You give it the region you want to show and it makes a zoom level that includes that whole region. Giving your desired region to <code>regionThatFits:</code> should return the level that it uses.</p> <p>If you're zooming the map with a pinch, you can get to a level between two zoom levels, but if you double-tap (to zoom in) or do a 2-finger tap (to zoom out) you will only see the "standard" zoom levels.</p> <p>I'm talking about zoom levels here, but really they don't exist in iOS in the same way they exist in Google Maps. Only regions exist as far as setting the map to a certain level.</p> <p>With your problem of getting the best fit for pins, I found that something changed in iOS 4, and the code I'd used to fit pins suddenly gave too much space. I divided the deltas by 3 and it worked again. You might want to wrap this in a conditional to target only iOS 4. </p> <pre><code>region.span.longitudeDelta = (maxCoord.longitude - minCoord.longitude) / 3.0; region.span.latitudeDelta = (maxCoord.latitude - minCoord.latitude) / 3.0; </code></pre> <p>Looking at your code, you use <code>* 0.9</code> to get the exact same thing.</p> <p>One of the strange things I found was that the value returned by <code>regionThatFits:</code> wasn't always the region that the mapview ended up setting. It might be a bug, but it's been there since iOS 4.0. You can test this yourself by logging the <code>MKCoordinateRegion</code> from <code>regionThatFits:</code> and comparing it to the mapview's region after zooming. I seem to remember it coming up on the Apple Developer Forums.</p>
    singulars
    1. This table or related slice is empty.
    1. POSlight zoom on MKCoordinateRegion?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USnevan king
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSlight zoom on MKCoordinateRegion?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COTo expand on nevan's answer, the map tiles are pre-rendered at a series of different resolutions which necessarily have discrete steps and as a practical matter often have pretty large steps (storage is cheap, but this is the *entire planet* we're talking about :)
      singulars
      1. PO
      1. USFrank Schmitt
    2. COIt's true, I should have said that. I think that the steps are all just a halving of width (to make the math easier). So zooming in a 512x512 tile uses 4 512x512 tiles to show the same area. This post has one of the best explanations I've ever read: http://troybrant.net/blog/2010/01/mkmapview-and-zoom-levels-a-visual-guide/
      singulars
      1. PO
      1. USnevan king
    3. COMuch appreciated, that makes perfect sense. Half my reason for asking was just to find out "why". Dividing the deltas by 3.0 zooms very far in for me, I will have a play and see what I can come up with, but at least now I am on the right track.
      singulars
      1. PO
      1. USfuzzygoat
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload