Guys can you help me with these? whats wrong here? Gamecenter window wont come all the way.
My app runs always on landscape. It works fine but the effin gamecenter will only show partially. I have no rotation problems and I dont care that the gamecenter loggin shows in portrait. I just want to show the leaderboard. Halp
Heres a picture of my problem:
http://i41.tinypic.com/raount.jpg
Related
I am developing application with QT5.11 and VTK8.2. There are 2 sub windows in the qmdiarea. Each of the windows has a QOpenGLWidget. First it behaves very well.
enter image description here
When I try to scroll the mdi area, one of the window becomes black.
enter image description here
I have spent a lot of time on it. However there is no progress. Can someone give me some tip about the issue?
Any help is appreciate.
Thanks
I have done a lot of research about the issue. First I suspect that the margin of the layout which holds the widget is not set 0. But it's the cause because the issue is still there even after I set the margin to 0. Then I search about the QOpenGLWidget and did some research about QOffscreenSurface and QSurfaceFormat. But I feel very frustrated because I can't figure out what causes the issue.
Im working with media queries right now and when i press inspect element to look how the site works from other devices it does not show as full-screen. Only half of the image is showing, which is so frustrated.
To let you know what i mean, heres a picture
https://imgur.com/a/tBBXL
Ive been trying to change the resolution but that doesnt help. it just shows how big of a window i have.
Been trying to change the resolution of the media queries im using but thats not working either.
Im using
#media screen and (max-width: 540px) and (min-width: 220px){}
But overall it does not seem to be the problem.
Figured out it was the settings in the chrome browser that caused the problem.
It was working for IE and firefox.
I'm working on an existing React-Native app, and in the iOS version, there's a problem where a portion of the bottom of the screen does not respond. At first it was thought to be on a specific screen, but upon further investigation, it was found to be affecting other screens as well. The control used on the first screen where the problem was noticed is TouchableOpacity, but a rectangular section in the middle at the bottom of the screen does not respond, but in either corner at the bottom of the screen it does respond. Another screen has a ListView, and if you attempt to scroll from that same bottom middle area, it won't, but everywhere else, it will. This is evident in both the simulator and on the physical device. It acts like there's something in the road floating over the top of everything.
I've tried using the Accessibility Inspector to identify the cause, but this hasn't revealed anything.
The highlighted area in the screenshot above is where I'm referring to.
To complicate things further, this problem doesn't exist in the Android version.
Has anyone experienced this before, and if so, what was the cause and how do I fix it?
Edit: I've now determined the cause is an Animated View that's hanging about, it seems not all the child elements within it are having their opacity set to 0. I've attempted to address this using pointerEvents, but this just moves the problem to a different child element.
Anyone have any suggestions?
The issue turned out to be that the parent was having it's height changed during the show and hide events to avoid this same issue in Android, so we need to only change it if the platform is Android.
this.setState({height: (Platform.OS === 'ios') ? 50: 0});
I am developing a webview app.
I need that the webview covers all the content (all the space available!) but I can't get to this...
I've tried several ways but stil don't understand how to tell the webview to autofit depending on the screen.
Here is my situation now:
And this if I rotate the device
I guess this means that I'm not working in the right way, eh ? Can anybody lead me to this right?
thank you
Add this 4 constraint like this for your webView.
I've been experiencing some very strange behavours in an app I'm developing. The app is not very advanced, it stores a couple of places in a sqlite database and is displayed in listviews, on a mapview etc. So, when browsing through my app after deploying it to my phone everything works great, but after a while one listview doesn't get inflated. A scrollbar appears as if the items were there but I can't see them. I push the back button to close the app. When revisiting the app my first view, which has two buttons, gets all messed up. The buttons fill the viewport and the background disappears etc. I can't figure out what's wrong.
Anyone else facing these problems? My phone is a HTC Desire HD with Android 2.3.5
The app is pretty "layout heavy", if you know what I mean. The listview items has custom background images, I'm using custom fonts etc. But the app is running smoothly up to the point when it freaks out and displays/don't display everything wrong.
My first thought is there is some kind of memory issue, ideas?
EDIT:
I believe this might have something to do with defining and using #00000000 as transparent color. Use #android:color/transparent instead.
SOLUTION:
So after doing some testing I found that what I previously mentioned in the edit really is the cause of this problem. I had defined the transparent color in my colors.xml as #00000000. This seems to work, sometimes... And other times it grabs a drawable instead, but not a drawable that is named "transparent", it grabs ANY drawable. Weird but true.
After some testing I finally found the cause of this problem. I had defined the transparent color in my colors.xml as #00000000. This seems to work, sometimes... And other times it grabs a drawable instead, but not a drawable that is named "transparent", it grabs ANY drawable. Weird but true.
So to fix this problem you should use #android:color/transparent instead when you want transparency on, for example, a view background.
If there are memory errors you should be able to catch them in logcat. You'll get "VM failed on xxxx byte allocation" messages (or the like).
Silly/stupid answer: often when I run into layout issues within my app, it's because I needed to do a clean build after having changed my layouts. You might want to start there.
Edit: You might also try the emulator, and if you suspect memory issues you could start the emulator with a small heap to force the issue to occur sooner. You can also check your heap usage in DDMS or with the Eclipse MAT to see if it's leaking.
I was experiencing the same problem on Galaxy tab even with #android:color/transparent. Was able to fix it only by replacing android:background="#color/transparent" with android:background="#null".