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.
Related
I don't want to hide time, but want to use full screen
In the storyboard on the interface controller settings I set the checkbox "Full Screen" and "Fixed to screen edges" to ON.
In the storyboard I can see the full screen mode is working and the WKInterfaceGroup is scaled to the entire display.
But unfortunately on the watch device/simulator it does not work.
The group has alignment center/center OR center/top and width and height are set to "Relative to Container"
How can I really use the full screen mode?.
I just have to add a label equal to Time in top black space. I want to show some text here. I have seen this in some other apps, They are using this space. Even in Apple design guide lines docs, they use this space. I am adding these reference screenshots also.
In above pictures, you can see they used this top space for titles. I also want to add a label to show some text equal to time.
Any help would be greatly appreciated.
This is a really weird bug. After digging around I've found a way to fill the whole screen. It's not pretty but I'm consistently getting full screen if i'm adding a sprite kit scene into a "main group". Again; it's not an elegant fix but it works and isn't really that resource intensive. Hope this works for you too!
I'm working on a UWP project which uses the MapControl.
After updating to the Creator Update for Windows 10, the mapcontrol behaves in unexpected and undesired ways:
I update the heading and center almost constantly, but this now causes the zoomlevel to change slowly over time.
And when I change the mapstyle, it zooms out by a lot. (But this seemingly only when I update either/both the heading and/or center)
I have no idea why this is happening or how to avoid it.
Any help appreciated.
This is a bug that is currently being investigated.
As a workaround, rather than independently setting zoom and center, try using the SetScene API.
like this:
TrySetSceneAsync(MapScene.CreateFromLocationAndRadius(newCenter, newRadius, heading, pitch), MapAnimationKind.Linear);
https://learn.microsoft.com/en-us/uwp/api/Windows.UI.Xaml.Controls.Maps.MapControl#Windows_UI_Xaml_Controls_Maps_MapControl_TrySetSceneAsync_Windows_UI_Xaml_Controls_Maps_MapScene_
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 looking to achieve the following :
when an application stars up, I want it to slide in from the left of the screen
Is this possible to do in linux ? How do I go about achieving it ? I could not find any resources online, so if anyone could point me in the right direction, that would be great.
I am open to programming a solution for this too. It would be great if i can get an answer on how to program something like this.
Presumably you have control over the placement of the window. Place the window off screen, then set up a loop that moves it over one pixel at a time. Exactly how to do that depends on your GUI toolkit.
I am hoping someone can help with this issue that I am having using xamarin.ios. I am trying to present a UIImageView on top of the current view once a button is touched. To illustrate what I mean, see the two screenshots from an app that does exactly what I want. The first shows the 'i' button next to Printers label on the navigationbar, that when touched the second screen as shown in the second screenshot appears.
Any help much appreciated.
I think what you want is a "popover".
Xamarin has a recipe for popovers on: http://docs.xamarin.com/recipes/ios/standard_controls/popovers/display_a_loading_message