I have installed a new Xcode version 11.1 in my mac and open my existing project, while i’m trying to open my storyboard its completely shown black UI.
had the same issue, all i did is
clear constraint, for my case the source was from UITableView, and make sure constraints are attached to safeare not superview.
from toolbar on the top go to Editor > Canvas > Layout Rectangle Very important you have to repeat this step 3 times
Quit XCode and reopen it again , all should be fixed
I've noticed this happen when i switch view for different devices 8, 11, 4s
Good luck
Related
I am implementing a splash screen for my app. I just came to know about storyboard constraints to support multiple devices. Basically, I feel it very difficult to understand it as a beginner in this, also I see there is no apt documentation in xamarin also. I want to know the steps to set an imageview width to its super view (View controller).
I see what I should do from here, Visual studio Xamarin iOS launchscreen storyboard layout. But, how do I add those constraints, totally no idea..?! Particularly imageview width and height to superview, trailing and leading
Now, I can only know how to set the constraints in designer by dragging, I'v only learnt to center the image to super view in X and Y (Horizontally and vertically). There is no button to add constraints. How to add leading and trailing constraints? I'm using Visual Studio 2017 for Windows
I got it working.
Step 1: Open storyboard file with lowest screen resolution device set (iPhone 4s) and drag & drop an imageview to fill the view controller.
Step 2: Set the uiimageview source from resources/image assets.
Step 3: Click on the image -> Properties Tab -> Layouts section. You will see like this
Step 4 : Properties -> Layout -> Under View group, there is title called Arrange, there is a autosizing box and example box.
Step 5 : You should click all the I-bars and lines in the center to make it red like below to fill the width (you can see that reflecting in the example box as you click)
Now, SAVE and then switch to other devices, you should have that UIImageview filling the device's height and width.
This will be very useful for important UI auto designs like splash screen.
I've encountered what might be a bug, but I do want to ensure there isn't a setting I missed somewhere...
I'm using JavaFX Scene Builder (this has the same behavior in Gluon Scene Builder), on macOS X High Sierra.
The Scene Builder application is operating in fullscreen mode, and when I press cmd+P to launch a preview window for the FXML project loaded, it opens normally, like so:
But if I put the preview into fullscreen (fills the screen space, not in fullscreen mode like scene builder app) by pressing the green plus at the top left, and then close it (or shrink back to normal size and then close), it reopens back in fullscreen.
My informal solution is to shrink the fullscreen window to normal size, then minimize the window (which also makes the screen black), then reopen the preview and then close it. That makes it open at normal size again.
My question is whether or not this is a bug. Is there a more simple solution or is this even the intended behavior?
Thanks.
My app has a multi-pane tutorial-style view that users swipe through to learn about the app. This is implemented very much as described in this tutorial. Having implemented it for both iOS 7 and 8, I'm comparing how they work, and finding issues with the latter — I'm running Xcode 6 GM here.
It seems that the UIPageViewController is rendering the views after the transition is complete. I overrode the delegate methods to see what was going on:
- (void)pageViewController:(UIPageViewController *)pageViewController willTransitionToViewControllers:(NSArray *)pendingViewControllers
{
NSLog(#"Frame size before: %#", NSStringFromCGRect([(UIViewController*)pendingViewControllers[0] view].frame));
}
- (void)pageViewController:(UIPageViewController *)pageViewController didFinishAnimating:(BOOL)finished previousViewControllers:(NSArray *)previousViewControllers transitionCompleted:(BOOL)completed
{
NSLog(#"Frame size after: %#", NSStringFromCGRect([(UIViewController*)previousViewControllers[0] view].frame));
}
And here's a sample output:
Frame size before: {{0, 0}, {600, 600}}
Frame size after: {{0, 0}, {320, 568}}
This manifests like so: swipe to the left to pull in the next view, and note a 32-pt white space at the bottom of the new view. Once the transition is complete, it jerks into its proper layout.
Is this a bug in iOS 8, perhaps? I'm all out of guesses at this point.
I figured out you need to base your constraints on the view and not the layout guide of your view controller. This will ensure your view controller respects the constraints you set prior to the transition in a PageViewController.
you can do this like so:
Remember to uncheck "Constrain to margins"
For anyone having this issue, for me it appeared to be that I was laying out views "relative to margin" (a new feature in iOS 8).
Instead of:
Use:
I've been struggling with this for a few days.
I tried to implement it by instantiating the page ViewController from the storyboard. There was a definite resizing occurring. Checking the frame size in
pageViewController:viewControllerAfterViewController
pageViewController:willTransitionToViewControllers
pageViewController:didFinishAnimating:previousViewControllers
The frame size would always change between the calls to 1 and 3. Sometimes before 2 and sometimes after.
If you're also using storyboards, I was able to resolve the issue by extracting the page UI elements into its own XIB file, setting the constraints in IB and then creating the pages with a call to initWithNibName.
Not a complete answer but it returned me to feeling productive.
Hope it helps.
For me solution was to pin top of the tableView to superview:
Editor -> Pin -> Top Space To SuperView (iOS8)
It is a bug in iOS 8 but I found a workaround:
Add an empty view on top of the statusbar in your Storyboard. The height of the view should be as much as the y-value of your object that is being moved.
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
I need help determining what the cause of a serious visual glitch is with one of my production websites. It is only happening with Safari - Chrome and all other browsers are fine.
http://www.philanthropicdirectory.org/search
This is a Drupal 6.x website, running the following simultaneously:
jQuery 1.3.2 (Drupal base/default)
jQuery 1.4.4 (This is used here and there by overriding the jQuery namespace to '$js' for certain advanced operations 1.3.2 can't handle)
jQuery UI 1.7.3
Thickbox 1.8.2.19 (I've slightly modified this .js)
TO REPRODUCE:
Click link (visit the page): http://www.philanthropicdirectory.org/search
Click twice (once to center) on any of the 5 'coverflow' panels to trigger Thickbox content
Once TB content loads, resize the browser window horizontally left or right
Notice the odd background-image and background-color offsetting
Switch between any of the 5 'tab' icons in the upper right of the modal system
At any point, use Web Inspector to uncheck and then recheck any CSS property, anywhere
Notice how this instantly clears/fixes all visual glitches
Resize the browser window again or tab between the other tabs, and notice the glitches return.
If you notice the same things I am, it'd be great to get your machine config and Safari version.
Before
After resizing
After tabbing
The images say it all, and as far as I could test, I can only reproduce this problem in the following setup, with Safari:
MacPro, 6-core Xeon (2010)
OS X 10.6.8
2 monitors: 1x 23" Cinema Display (old silver one) + 1x 27" Apple Cinema Display
ATI Radeon HD 5770 (Mac version w/01.00.436 Driver)
Safari 5.1+
I've tested other machines and other machines with earlier versions of Safari (4.x), and the problems are simply not present.
Is there anything you think I can test to figure out why this is happening?
PS: Only using one monitor at a time produces the same problems.
SOLUTION!
I noticed this happening with another website we've built - a website with nothing in common with the Drupal one with the problem here, save for the fact that this new one also has a Flash (SWF) file in the body, and I was applying a CSS property to an element with a negative z-index value.
It was happening on this new website because the container for the object in the HTML was set to
z-index: -1;
in order for elements positioned to overlap the object could be clicked on (otherwise, links on top of the object could not be interacted with).
I was able to permanently fix it by instead setting any elements positioned on top of the object
z-index: 1; /* or anything > 0 */
Given that solution, I hunted down any and all "z-index: -1" CSS on the Drupal website and sure enough there was an element within the Thickbox container that was shown on every tab - the big green "SEARCH" input button. It was styled that way because of visual needs (something to do with the fake inner-drop-shadow on the button).
I disabled the entire z-index property for this element, and lo-and-behold, the funkiness permanently disappeared on the Drupal website.
Hurray! It was surely providence that I came across the same issue more acutely on a different website.
Now I'm not sure the exact bug in Safari that is behind this without intense testing, but all I do know is that an object on the page + any element near it set to z-index: -1 equals total meltdown (on a Mac running Safari 5.x).
I checked in Safari 5.1 (7534.50) on an HP Xeon running Windows 7. I don't see any glitches.
That's weird. Sounds like a race condition of some sort. Maybe there is a bug in your ATI driver? Since it fixes itself when you re-render it, perhaps you could introduce some delay somewhere which might give it more time to render properly?