I'm developing an app on the iPad, and trying to detect multi-touch events. The events are working fine, but in the simulator, I'm not getting the little circles that show you where you're touching. Not so much an issue for single touch, but for multi touch, it's a big pain. Any idea why these circles aren't showing? I think it's something with my machine (MacBook Pro), because on another MacBook Pro, the circles do show up.
Edit
I've discovered that this problem only happens if the scale is set to 100%; if I set the scale to 50%, the circles show up.
Related
A while back, when we were first testing our app, the screen used to rotate when we tilted the phone. Even if the portrait formatting wasn't so great, it still responded to the orientation change.
I have no idea what happened between that point and this, but it no longer responds to orientation changes, at all. If I tilt the phone, it stays in portrait mode and does not rotate at all, the text does not align to the new orientation.
This is across all platforms, and I have the proper settings selected for each specific platform (in iOS in the info.plist, and in Android with the MainActivity decorations.)
The one thing I did do is that moved all of my screens from StackLayout-based to FlexLayout-based. But the screen SHOULD still rotate, or at least ATTEMPT to rotate, should it not? And this happens across all screens.
So ... if I may please could get some advice about what may be happening, here, that causes this behavior across all platforms?
It should be noted that we are also using Telerik libraries for many of our controls (but I don't know why it would make a difference.)
Also, it's a shared app.
Issue solved. Rotation was locked.
Search done. Nothing in the archives like this. I've screwed up a previously working site. I know not how. Specifically, rotating my iPhone 6 from portrait to landscape displays my site narrowed to about 50%. Reloading pops it out to normal presentation. Rotating back to portrait, and then returning to landscape, requires another reload. Never had a problem where all viewports work yet a kick in the ass required after a rotation. Site is CodeStruggle dot com. I have the small and medium backgrounds set to tan and pink for trouble shooting. Thank you for any help.
Found the problem. For some reason my horizontal rule would not work. So I substituted the creature below until I could investigate the <hr> problem. Everything performed perfectly on desktop, but not on my phone. Live and learn.
<p class='fake-horizontal-rule'>_________________________________________________________</p>
p.fake-horizontal-rule{
color:#ccc;
text-align:center;
}
The base deployment of the app is iOS 7.0 and both device and the simulator are using 7.0.
The translucent effect on the simulator gives a blur to the content under UINavigationBar, but on the device, no blur. I've noticed a couple other difference tool. My UIToolbar was translucent on the simulator, but opaque on the device and there have been a few times where tints don't match.
For the nav bar though, why is it different and how do I get the blur effect? Without the blur, text under nav bar text could be distracting and confusing!
After much digging, this is a hardware limitation. The blur effect is not enabled on the older devices due to GPU requirements/performance.
The blur effect will appear on:
iPhone 4S and newer
iPad 4th Generation and newer
all iPad Mini
Now i am using macbook pro with 13 inches.
Yesterday i upgraded XCodes version to 4.3.2.
In that iPad Simulator is too big and iPad Retina Simulator is also too big.
It's not fix my screen.
iPad Retina Simulator size is take all of my screen and it's can only show iPad's dock.
I can't see overview iPad screen.
I always scroll down and up to test.
When i change Simulator's Window > Scale into 75 %, It's still too big.
50% is too small and can't see anything clearly.
When i develop with XCodes 4.2 , iPad Simulator is fix size and okay to test.
I want iPad simulator size fix my screen.
Is there anyways?
If my question is out of question, so sorry for that.
Thanks.
Maybe it's because the iPad 3 have a really large resolution (2048x1536). That's more than most computer screens. You will need to zoom out to display the entire screen just because of this, or you must get a larger (higher resolution) screen for your computer if you don't want to scale the program.
The reason for this is that the iPad 3 have much tighter pixel density than most other computer screens so each pixel on the iPad is smaller than each pixel on your computer screen.
What you can do is make the simulator start by suppressing the title bar and your dock if it happens to be shown.
Follow these steps, please be responsible and back-up your files before editing anything as I do not take responsibility for things going wrong.
Before you start close any running simulators.
In Finder Press CMD+SHIFT+G and enter the folder /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneSimulator.platform/Developer/Applications/iPhone Simulator.app/Contents/; this folder may differ for you depending on your location of the simulator/SDK.
Backup the file called Info.plist
Copy Info.plist to your home directory.
Double click Info.plist in your home directory. You will be presented with the plist editor.
Select the first entry called Information Property List and click the plus (+) sign immediately to the right.
Enter Application UI Presentation Mode into the Key field of the new entry, tip: it will auto populate after typing Application UI.
Enter 4 in the Value field, this will then change to All Suppressed.
Save and close the file.
Replace the original plist file with this new one, remember to back the original up first.
Now when you run the simulator it will not show the menu bar when it becomes active. The reason you needed to copy the file to your home directory is because you do not have write permission to it. It also stops you mucking it up and preventing the simulator running while editing the file.
You can apply this trick to any application by finding it's plist file, thus I also change Xcode.app to do this too.
You will need to scale the simulator to 75%, however it will now be almost the full height of the screen with no loss of the iPad window.
Now It's more flexible with Xcode 9- Simulator. You can pick & drag any corner or simulator to resize it and set it according to your requirement.
Look at this snapshot.
https://apple.stackexchange.com/questions/205865/ios-simulator-screen-size-not-equal-to-window-size
Really not sure why this is occuring but with some systems the backround image gradient appears choppy and only half of it even appears, also some systems display the color so light is can barely even be seen especially those with lower resolution settings. Any ideas why this is occuring?
Here is the link to the page: http://www.kapacitive.com/Main_Page_Template.html I have it here just for testing purposes.
I also noticed that if I change the CSS positioning of the background to background-position:50% 50%; the issue of only having half the backround appear occurs on my main system.
I have a small touch screen Garmin device that has a web browser and with that device the background appears both choppy and only half appears, though I really didn't expect much from that device in the first place.
My secondary machine has a lower resolution display and with that system the background can barely be seen. This also occurs using an entirely different machine and display which has a lower resolution setting.
Maybe, I should just trash the background all together with all these damn bugs occuring, though in my opinion it does look better with the background.
If anyone wants to volunteer test the page using other devices and provide the results that would also be cool, I currently do not own any Apple devices.
Like I've stated any suggestions or ideas on resolving this issue would be great and even any insight about why this is occuring. I realize each machine is different but the differences in how this page is rendering between different machines is way too drastic in my opinion to be acceptable for deployment.
I believe the problem is with the color-depth of the machines viewing the background image. That nicely faded gradient relies on a LOT of colors, and on a screen with a limited palette, it's going to be choppy.
A work around would be to test the pixelDepth/colorDepth of visitors' screens, and to dynamically change the background image to something plainer if it is too low. Most browsers provide that information [via JavaScript] in the screen variable.
window.screen.colorDepth
window.screen.pixelDepth