I'am programming one kiosk app using GTK+Ubuntu 10.10. All works ok when I run the app manually but If I setup it up as a Startup Application on Gnome, it does not become fullscreen. I'am using gtk_window_fullscreen() function to tell it to resize as a fullscreen window. When Gnome starts, it launch the app with its default size without resizing.
Calling gtk_window_fullscreen() a second time, some seconds after being launched, doesn't work.
If I move the mouse pointer over the window once opened, it resizes automatically to a fullscreen status.
Any idea how to get a fullscreen on startup?
Regards
Fullscreen is handled by the window manager, so you may need to make sure your program is launched after the window manager has started.
Related
I have some performance problems running my Flutter application inside iOS simulator installed inside a VirtualBox OSx machine. The simulator run and the application is deployed without any problem. But there is lag when the screen has to be redrawn. For example, when I click on a button which opens a modal sheet, the image is stuck, I can unlock it simply dragging the IOs bottom bar of a few pixels. It's difficult to test the application since every time I have to move that bar a few pixels in order to update the phone image. This is an example of my problem:
As you can see the image is redrawn just after I click and move the iOS bottom bar.
Here a simulation of a native iOS app:
Here as you can see the screen has to redraw, I don't need to move the bottom bar.
Any suggestion?
Anytime I start the Unity application on my MacBook Pro the console ends up expanding, till it has finished loading, preventing me from accessing any other application till I minimise or close it. How can I prevent this from happening, so that the console doesn't expand fullscreen when launching Unity?
This is an issue that happens to me just sometimes, most of the times the emulator works ok.
screenshot of the problem with the emulator
The thing is, that the emulator starts but it can not be maximized. It doesn't matter if you click on its "window" from the Tasklist at the bottom or you try to force it to maximize/make it go to the front from the Task-manager; it just doesn't react to it.
In the little window that appears when you have the mouse over the task (see screenshot), you can even watch the emulator starting and waiting for the interaction with the clock and so on, but it is not accessible.
Any ideas?!
I had the same issue after forcing the emulator to close during debugging.
To fix the problem, try changing the screen resolution of the virtual device under Edit in the AVD manager and then launch the virtual device.
This fixed the issue for me and I was able to revert to the original resolution without any problems.
When i start my app for the first time after installing it and exit before the splash screen disappears, from then on launching from the multitasking menu it comes up with a black screen. If I click on it from the home screen it loads fine but every time I try from the multitasking menu it is a black screen until I terminate it. If I add the UIApplcationExitOnSuspend property to the properties list the black screen continually appears until i restart the device. Any help is appreciated.
Thanks Sj
A couple things:
You probably don't want to suspend your app prior to the splash screen disappearing. applicationDidFinishLaunching is running code (you know, like adding a window to the app) while the splash screen is showing. If you suspend it early, it doesn't have a chance. This may not be the case after the first time install but if I were you, I'd give it the time it needs to do initial install instead of interrupting it.
Another less likely scenario: Are you doing this while the debug is still running? I've only had an issue similar to this (black screen after suspend) if I leave debug running and then suspend the app to the background. As soon as you bring it back out of the background, you get a black screen, so in that case it's a bug. If you hit the stop sign button in XCode to kill the app, it worked fine after that.. but you have to kill it before suspending it.
My guess is your likely cause is #1. Give the app more time to do the initial load. After that, it should be fine. For whatever reason, the first time installing/loading is always the slowest.
Is there a way to programmatically set the iPad to run the iPhone app at 2x as it is launched (yet keep the iPhone app native). I understand I can create NIB files for each hardware platform, but for ease, I just would rather the app launch as if the user had tapped the 2x on the iPad. Thanks...R.J.
No. The pixel-doubling malarkey is not under your app's control, and is pretty much a crutch for apps that weren't designed for the iPad. If you didn't go nuts with specific pixel measurements in the original code, it shouldn't be difficult to move to the larger screen.
It's not quite program control, but you can get an app to start up in 2x mode on iOS 4.2.
I've had a couple of apps that have always started up in 2x mode, and very nice it was too, but I only worked out why this was today!
Steps:
Run iPhone app (e.g., from Xcode)
Use '1x' and '2x' buttons to select desired zoom level
Press home button to get back to launcher
Double tap home button to bring up task manager
Kill your app (hold finger down until icons start to dance, then press the '-' button on your app's icon)
(If you ran under the debugger in step 1, Xcode will tell you the program got a SIGKILL, and might stop somewhere random in the call stack; you can ignore this.)
Now next time you run the program, it will start up with the zoom level you selected in step 2!
I didn't test absolutely every method of closing the program, but this preference doesn't get saved if you stop it from Xcode (e.g., using Run|Stop menu item), and it doesn't get saved if your program terminates using exit. Closing it using the launcher is the only way I've found so far...