I am using the following:
MyProfileSettings.TrySetWallpaperImageAsync(myStorageFile);
To change the Wallpaper on both Windows 10 PC, and Windows 10 Mobile successfully However, when I debug the app on my Xbox One, it doesn't seem to change the Wallpaper. Is programmatically changing the wallpaper on XBox one supported?
The feature is not yet supported on Xbox but should at some point (no date available)
You can find the list of the not-yet supported features here : https://msdn.microsoft.com/library/windows/apps/mt693377
Related
I've got an industrial panel which running a 32-bit version of Windows Embedded 8 Standard. It is required to use the internal speaker to make beep sounds. Connecting external speakers is not an option.
Previously this was running XP based Windows Embedded Standard and using Console.Beep in C# will use the internal speaker. However in Windows 8 Embedded Standard this seems to use the external speakers instead, despite not being connected up.
The internal speaker is still operational - the touchscreen driver (eGalaxTouch) still uses the internal speaker when tapping the screen, however I cannot replicate this in my own application.
I've tried the following from a C# application with no effect;
Console.Beep()
MessageBeep() (user32.dll)
Beep() (kernel32.dll)
SystemSounds.Beep.Play()
I understand this is not possible from Windows 7 64-bit onwards, but I'm using 32-bit OS here and it still works with the touchscreen?
While a solution in C#/.NET would be ideal, I'd be up for other solutions (C/C++/whatever).
Typically shortly after posting the question, I find an answer...
Basically, using the 'Beep.sys' file from the Windows (XP) Embedded Standard in place of the Windows 8 Embedded version allows Console.Beep to work as expected.
harrymc's answer to a similar question https://superuser.com/a/230167/83606 below. Note that there is no 'Beep' device in the device manager in Windows 8 (Embedded), but the procedure is otherwise similar.
From Default Beep PC Speaker changed in windows 7 – How to get back to old style :
The default beep is controlled by a
driver under,
c:\windows\system32\drivers\beep.sys.
Maybe if you switched it out with a
driver from XP/Vista it would increase
the volume.
To see this driver you have to open
device manager then click on View >
Show hidden devices. Then under
Non-Plug and Play Drivers you’ll see
“Beep.” This is the driver that runs
your beep. Right click on it then
choose properties and go to the driver
tab, then click on Driver Details…
This shows the file version which
looks like it’s been change with
Windows 7. So replace it with an
older version and see what happens.
Procedure to follow :
Boot from an UBCD4WIN disc (or BartPE if you don’t have an SATA hard
drive)
Take ownership of the “C:\Windows\System32\Drivers\Beep.sys”
file and give the local
“Administrators” Group “Full Control”
permissions.
Rename “Beep.sys” to “Beep.old” (just in case)
Copy “Beep.sys” from an XP machine to this location.
I'm trying to find way how to programmatically dim screen in the UWP app, but I can't find any related API... is there anything like that?
In newer versions of UWP API this is possible, please see:
UWP > API reference > Windows.Graphics.Display > BrightnessOverride
Windows 10 requirements:
Device family
Windows 10 Creators Update (introduced v10.0.15063.0)
API contract
Windows.Foundation.UniversalApiContract (introduced v4)
Update:
This is possible since Windows 10 Creators Update, see https://learn.microsoft.com/en-us/uwp/api/windows.graphics.display.brightnessoverride.
Unfortunately, there is no such API that can control the screen brightness in Universal Windows Platform (UWP). As #Rafael said, the screen brightness is thought to be a global setting controlled by the System Settings. And in some device families such as IoT, the device even may has no monitor.
If you want to dim the screen in your app, you can try to add a dark overlay on top of your view and control its opacity. Also, you are welcome to vote on UserVoice to ask for this feature.
I would like to create a ScreenCaptureLib.dll which is intended to be built for Universal Windows.
We already have the following using Windows.Forms:
https://github.com/ShareX/ShareX/tree/master/ShareX.ScreenCaptureLib
Obviously none of the Windows Forms code does not work and I would like some pointers in the right direction to get started.
You may follow the official document for Record the screen with ScreenCapture, but please notice that:
The ScreenCapture API is only available on mobile devices.
And for now there is no API can be used directly to capture the screen on a desktop from an UWP app. However, as a workaround method, we can render the XAML tree to a bitmap, to do this, please refer to Capturing Snapshot in Windows 8.1 Store App.
You may also submit a request to add this new feature for developing through the Windows Feedback tool.
Update:
The ScreenCapture feature is only supported for mobile devices running Windows Phone 8.1. This API is not supported on Windows 10.
I am developing a Windows Phone 8/8.1 Apps, I am able to customize the background of the lock screen and etc. But when I saw the app Live LockScreen beta by Microsoft I found its to be very good and inspire me that I can customize my lockscreen similar kind with standard clock customized and much more improve features.
However I don't know what API it's used, I search in internet - no help.
Any idea how can I get some API so that I can customize my lock screen Apps in Windows Phone, No background change API, but other features like Text, Clock etc.
Thanks
I hope you're aware that, there's no such API being published yet which contains those features like in the Live LockScreen Beta as of now.
I have built an application that uses the GestureRecognizer (System.Windows.Ink.GestureRecognizer). The problem is that when testing it on some machines, IsRecognizerAvailable returns false. These systems are running .NET 3.5 and 4, so updates shouldn't be the problem. Can anyone tell me how to specifically install the GestureRecognizer component on systems where it is missing?
What is the OS on the machines where you don't get Recognizer. What I know is that Windows Ink support is limited on Windows XP/2K (its available on XP Tablet edition) but should be present in vistas onwards. Quoting from the link: http://msdn.microsoft.com/en-us/library/ms701189(v=vs.85).aspx - essentially indicates that gestures will not be available in windows XP.
Reduced Feature Set
Ink-enabled applications treat mouse
events as pen movements to simulate
working with a tablet pen. Users can
add ink, erase ink, and save ink
documents. However, recognition and
gestures are not available for users
other than those running Windows XP
Tablet PC Edition.