Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. CO@ Art: Thanks for your input. That definitely allows me to create the binary and install it on an iPad, but the only problem is that there is no 1x/2x circle-button in the lower left hand corner. Instead, it's just sized for iPad use. I want it to appear as a 1x view, and give the user the opportunity to press the 2x button to super-size it to the iPad screen. Any ideas? Thanks again.
      singulars
    2. CO@DZK - My mistake, I should've read that more carefully. I just created a new from-scratch iPhone project with the Base SDK set to 4.0 and deployment target set to 3.2 and it installed onto my iPad fine—with the 2x button and everything. Grab the Info.plist from your app's bundle. What's the generated value for MinimumOSVersion? This should correspond to your deployment target setting.
      singulars
    3. COOk, I've been working on this for days now. I definitely do not want Deployment>Targeted Device Family>iPhone/iPad as it supersizes a brand new app to iPad (I want the 1x/2x button to appear). When I set Deployment>Targeted Device Family>iPhone on a new app, I get the 1x/2x button just fine on the iPad. However, my current app -- even when I reproduce all the settings (including UIDeviceFamily set to 1 in the info.plist) only displays for iPad (no 1x/2x button). Consequently, 320x480 backgrounds only cover part of the background, etc. Not sure what to do next. Any ideas?
      singulars
 

Querying!

 
Guidance

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