I am programming in mac OSX using VSCode and XCode. I am using a iPhone 14 pro MAX to emulate my app on a device. I have some screens that they dont fit in the screen so the user have to scroll to see the whole screen. Now, I want to take a printscreen of this screen but not just the part of the screen that the user can see, but the whole screen, so when I see the print screen I am able to see the whole screen. Is this possible?
Related
I am currently taking screen shots for my application using iOS simulator. The issue I am coming across is that they are being being taking with borders and causing it to be rejected.
I have another approved application with screen shots and it doesn't have rounded borders.
I am using this button to take screen shots
Try to run the iOS simulator in the Mac and then take the screenshot. I did a test and the screenshot in the mac does not has the rounded borders.
Another way is you can use some tools to edit those screenshots to achieve what you want:).
This worked up until yesterday.
Before and after updating to MacOS Sierra 10.12.5 did not solve problem.
Config / Specs:
Macbook pro OSX
Dell monitor
iPad using Duet app
Previous functionality
I could expand fullscreen any app/program in Mac (the green button top right) and use 3 fingers on the trackpad to toggle between 'screens' on that individual physical screen.
Current bug
When I fullscreen an app on one display and swipe with three fingers, swiping controls all 3 physical displays. The display in question swipes to the app, but the other two displays also swipe to the right showing blank black or white backgrounds and are mouseover-able.
Desired functionality -- the Previous Functionality
Swiping on a screen only controls that display.
Had the same issue, there is a setting in Mission Control -> Displays have separate Spaces, checking this solves the problem for me.
I'm opening a topic here to find some help regarding the Splash screen on iOS. Apparently, all the process seems to be quite simple, but unfortunately, I've encountered a problem just on a specific case : the default splash screen is showed on the iPads with low resolutions (iPad , iPad 2, iPad Air , ...), the custom one is not set.
Specificity : The application is developed with React Native (Framework) only for iPad on a Landscape mode.
Here below you will find the steps that I followed to achieve the Splash screen :
2 pictures prepared for the Splash screen : Default-Landscape.png (1024*768px) & Default-Landscape#2x.png (2048*1536px).
Project opened on Xcode : MyProject.xcodeproj
Check out the folder "Images.xcassets" in the project.
Left click (2nd column from the left. In the full display interface) > App Icon & Launch Image > New iOS Launch Image.
Two new things appeared: one drop zone and a checklist with the devices that we wanted. Then I've chosen what interested me.
Drag and drop the images in the specific drop zone related to the good format.
After the image uploaded I've click on project "MyProject" (1st column) > click on target "MyProject" (2nd column) > click on "Use catalog assets" (button on the 3rd column) > select "Migrate" > then in the drop down menu I've chosen the settings that I've prepared before "LaunchImage".
Finally I removed the folder "Base.lproj" where the default splash screen (LaunchScreen.xid) was.
Result: After compiling, I've seen that the Splash screen was working for the high resolution devices (iPad Air 2 & iPad Pro), but unfortunatly, on low resolution (iPad 2, iPad Air, iPad Retina), I still have the default screen "NameOfProject" as headline and "Powered by React native" on the bottom of the page.
I really hope that you can help me on this one because I really don't know what's going wrong there. I've tried different import methods, differents sizes and names for the images. But still nothing work.
You may have to delete the app from the Home screen, and then reinstall it. iOS seems to cache the previous launch image for some reason.
Also make sure that your image sizes are correct if you haven't already.
Thanks a lot rclai89!!
Just to add some details to complete this topic. This video explains what you've advised me and solved my problem : https://www.youtube.com/watch?v=yiSehGHZZ18.
App removed from the Home screen : Once the emulator is running, on the top navigation choose Simulator > then Reset Content and settings.
Cache cleared : CMD + SHIFT + K
Derived Data cleared : On Xcode go to the Window item (top navigation) > select Projects > next to the "Derived Data" you have the path where the file is contained, just need to click on Delete button and everything is done.
Close & Re-Open Xcode. The next compilation for all the different devices (in my case iPad) show up the splash screen that I wanted. Awesome!
When I run the iPhone retina simulator in Xcode it stops if from moving above the top of the screen, but the simulator window is bigger than my monitor, so I can't see what's at the bottom of the simulator window, how can I change things so I can move it upwards off the top of the monitor screen?
You can always use cmd+2 or cmd+3 to fit simulator to your screen.
You can scroll the Display of the Simulator with the two-finger scroll.
Can look like this on a 15" retina
I am running xcode 4.3.2 and just started having the following problem.
All projects running in the simulator are positioning the popup keyboard in the center of the IPAD simulator. The IPHONE simulator is fine with the normal keyboard positioned at the bottom of the screen. Even a simple new project with a single text field shows the keyboard in the middle of the screen with equal amounts of white space above and bellow. This occurs in all orientations.
Interestingly, UIPickerViews also exhibit the same behavior.
This is driving me nuts, as it has been fine for many months and now all the objects (text fields etc.) are hidden when the keyboard plops down smack in the middle of the screen.
Please help. Thanks in advance.
Tom
This is a feature of the iPad. You can "drag" the keyboard with the drag handle in the lower-right hand corner of the keyboard. The image from this blog post by Rob Rogers indicates how to use it. My guess is you inadvertently moved your keyboard.