I am developing an UWP application in which i used graphics capture picker to select the window to record, but i want, when some one select window then UWP application should get minimize and that other display should come into focus
If the user minimizes a uwp app or switches to another app, this uwp app will be suspended. Besides, GraphicsCapturePicker control must be called from a UI thread, which means it will prevent the GraphicsCapturePicker control from appearing if the uwp app is minimized.
Therefore, I have to say that there is no way could implement your requirement.
Related
I am currently working in a UWP application. I have a situation where I need to open the taptip keyboard. The device needs to be in desktop mode and the keyboard should open on a button click. Is there any way I can achieve this functionality?
I know it works fine in tablet mode when a text box gets focus but I need to get it done in desktop mode and on a button click.
I know it can be done from a console application using System.Diagnostics.Process but I need a way around for uwp app.
The user can enable the tip to show when a text box gets focus in a desktop app by setting the "Show the touch keyboard when not in tablet mode and there's no keyboard attached". Apps should generally defer to the user's preferences on this rather than trying to override this themselves.
That said, you can show and hide the InputPane via the InputPane.TryShow and InputPane.TryHide methods.
You'll do essentially the same from a desktop app via the IInputPaneInterop and IInputPane2 interfaces. Launching tabtip.exe explicitly is limited and not generally recommended.
I have a UI design that I created to mimic the way that apps in Win10 look but in Win7 - 8. I created a Menu that drops down and has several buttons in it. When this drops down it's the height of the app itself. If the app happens to go behind the task bar the menu drop down opens up instead of down. Is there a way to change this behavior so that no matter where the app is located on a screen it will open down even if that means behind the taskbar.
Thanks
i have an app that is intended for a pc with a touchscreen display. I have a built in keyboard for the app. Every time i click a textBox windows displays the icon for me to open windows keyboard. How do i disable that from poping up in my app, BUT still let it pop up outside my app?
More info:
I have a kiosk style app, for employees to register gas consumption. and is all made for a tactil screen. When i click either a textBox or a comboBox the icon prompting me to open windows keyboard pops up. I want to stop that from happening since the app already has a keyboard. However, employees can still get access to regular windows, so when they do i want this pop up to happen naturally on the rest of the computer. So, i just want to stop this from happening in my app, and all the solutions i have came across are for windows in generally and not app specific. How to stop this icon from poping up in my app?
we have a legacy application done in VB6. When we add new windows to this application we create them with WPF and we expose a COM interface to open it from VB6. The problem is that the first time a WPF window is opened it takes a while as the system needs to load the WPF run-time.
Is there a way to load the run-time in background so the user does not has to wait when opening the window?
Thanks.
Some ideas:
Create hidden WPF windows when VB6 application starts, so WPF will load while user will do something else in application.
If it will not work with hidden window, you still can create WPF window with positon like new Point(10000, 10000), and select to not show this window in taskbar, so this hidden WPF window will force .NET to load WPF engine.
So, you can create invisible WPF window in background when application starts, and user will not have to wait later.
I am trying to create a parent WPF/surface application which will host multiple WPF/surface applications. I am looking for some pointers of how to implement such functionality. Was reading http://msdn.microsoft.com/en-us/library/ms742522.aspx but it talks about hosting Win32 content in WPF and vice versa.
My idea is to have something similar to MDI forms where you have a main form and you can instantiate multiple child forms.
In my case, these would be different applications which will be launched using a config file and loaded within the main application.
Also, since is there a way to ensure that the main window's process memory is not hogged by the child process initiated.
Edit:
The host application will launch different applications based on what user selects. One can say its like an application launcher which are build on WPF/Surface touch SDK. Now once the application is launched the launcher goes in the background(except showing small button to bring it forward again at some point later) and when the user ends the current application launcher comes back again in foreground. The only interaction i feel which is necessary is knowing the launched application is terminated or invoking applications in a limited screen area. If someone has seen the Microsoft surface application launcher, even when the application is launched there are corner buttons which bring the app launcher to foreground.
I would first look at using Microsoft Prism, specifically the Modularity namespace.
Except for the "different applications" part, it sounds like a classic case for MVVM. Are these "different applications" actually separate applications, or could they simply be separate projects within the same application? That may simplify the choice of presentation.
I suppose you could still have a View called "Host" that presents a different app.
Of course, WPF doesn't have the concept of MDI, but you can open multiple, non-modal windows.
It really depends on what you mean by "hosting". Does the main window need to somehow handle and/or interact with the other applications, or is it just a launching pad for other applications?
I followed this approach to solve this problem. The launcher was not hosting the application within itself but would launch a new application and hide itself.
Steps I followed:
The main launcher application will run in Kiosk mode i.e always on top/no option to close by capturing the close event/No instance shown in taskbar/no title bar/killing the explorer.exe/hiding the taskbar.
The launcher populates a horizontal listbox (data templated for UI) which lets occupied main center area of screen and can be scrolled either ways.
When user selected an item on listbox, click/tap event a separate process is launched with launcher window's visibility set to hidden and a small button(basically a window with just a button inside and size set to height/width of button) created on the either corner of the screen with always on top option.
The functionality of button is to minimize the current working application and set visibility of launcher back to visible and setting the focus to this window.
Since the process is launched by launcher, i trap the close event for the launched window to know user ended the application and then again pop up the launcher back.