This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 13%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
As shown in the image, I wrote these codes, which contain AppWindow.TitleBar.SetDragRectangles, and I'm sure that this code is working correctly, but these codes are not doing what they are supposed to do.
Why is this? I would like an answer from Microsoft, please!
By the way, I've heard that this is also affected by the DPI of the screen, how can I avoid this problem?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(179.20000000000002, 34%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXY%3C/text%3E%3C/svg%3E)
I cannot reproduce with the Windowing sample. Can you reproduce with the sample?
Oh, I raised an issue on GitHub that you can refer to.
I still cannot reproduce.
If so, you can use the app I developed to test the title bar, which uses Windows App SDK 1.4 and should reproduce this problem.
If it still doesn't work, then this may be a problem with the system.
You need to open my repository, switch to the Preview branch, then open the entire project with Visual Studio, manually install the Community Toolkit Labs NuGet package, and start running, if SetDragRectangles doesn't work, then you can't click the two buttons in the upper left corner.
so now I'm starting to wonder if Microsoft introduced some way to replace this "deprecated" SetDragRectangles?
It has been replaced by InputNonClientPointerSource
I tested by updating MSDN sample and it seems to work (still on Windows 10 only)
IntPtr hWndMain = WinRT.Interop.WindowNative.GetWindowHandle(this);
Microsoft.UI.WindowId myWndId = Microsoft.UI.Win32Interop.GetWindowIdFromWindow(hWndMain);
var incps = InputNonClientPointerSource.GetForWindowId(myWndId);
// In SetDragRegionForCustomTitleBar, same MSDN code with dragRectsList... dragRects
incps.SetRegionRects(NonClientRegionKind.Caption, dragRects);
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(316.8, 93%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
I am getting a invalid cast exception.
WindowsAppSdk 1.4.231115000
net8.0-windows10.0.19041.0
Exception thrown: 'System.InvalidCastException' in System.Private.CoreLib.dll
Exception thrown at 0x00007FFDFDA2CF19 (KernelBase.dll) in WebDive.exe: WinRT originate error - 0x80004002 : 'Specified cast is not valid.'.
Microsoft.ui.xaml.dll!00007FFD4E3D9A1E: CallContext:[\ImageDecodeActivity] 80004002 - No such interface supported
The program '[27812] WebDive.exe' has exited with code 0 (0x0).
this is the debug view
I cannot reproduce with the following code.
IntPtr hWndMain = WinRT.Interop.WindowNative.GetWindowHandle(this);
Microsoft.UI.WindowId myWndId = Microsoft.UI.Win32Interop.GetWindowIdFromWindow(hWndMain);
var incps = InputNonClientPointerSource.GetForWindowId(myWndId);
// In SetDragRegionForCustomTitleBar, same MSDN code with dragRectsList... dragRects
var appWindow = this.AppWindow;
appWindow.TitleBar.ExtendsContentIntoTitleBar = true;
//Set the window drag area
if (AppWindowTitleBar.IsCustomizationSupported() && appWindow.TitleBar.ExtendsContentIntoTitleBar)
incps.SetRegionRects(NonClientRegionKind.Caption, new RectInt32[] { new RectInt32(0, 0, 100, 40) });
Where is the code with IsCustomizationSupported and ExtendsContentIntoTitleBar ?
Like in MSDN sample : https://learn.microsoft.com/en-us/windows/apps/develop/title-bar?tabs=wasdk#interactive-content
Here, I am using AppWindow.
Are you sure SetDragRectangles is correct (it starts at x = 80) ?
If I copy/paste the MSDN sample (I added a rect rectangle to check the caption size, height = 48 in the sample), it seems to work fine for me (Windows 10 22H2) :
)
I think I'm right because it works fine with Windows App SDK 1.3.
What @Castorix31 suspects is reasonable.
Change to
m_appWindow.TitleBar.ExtendsContentIntoTitleBar = true;
//Set the window drag area
if (AppWindowTitleBar.IsCustomizationSupported() && m_appWindow.TitleBar.ExtendsContentIntoTitleBar)
m_appWindow.TitleBar.SetDragRectangles(new RectInt32[]{new RectInt32(800, 0, ScreenWidth - 80, 40)});
Unfortunately this doesn't work on my computer :(
The draggable area of the title bar remains in its default state instead of its custom state.
So, I went to collect some information and found that SetDragRectangles was marked as "deprecated", and I found that your systems are all Windows 10, only I am Windows 11...
But after I packaged the app to Windows 10, it still hasn't changed.
I don't know what's going on now, it's weird, it seems like only my computer will have a problem, so now I'm starting to wonder if Microsoft introduced some way to replace this "deprecated" SetDragRectangles?
My system is Windows 11 Enterprise 22H2, OS build 22621.2134. I also cannot reproduce using your application. If there are, it should be highlighted at AppWindowTitleBar.SetDragRectangles(RectInt32[]).
If so, I temporarily publish an app, you download and run it, and see if the above problem occurs.
https://github.com/BadMC-Studio/BadMcen-Launcher/releases/tag/Preview(Canary)-0.0.1
Thank you for your patience!
Thank you! I did it!
The published application which behaves like the build in my answer also cannot reproduce the behavior. Does @Castorix31 's workaround work for you?
Yes, I did it, I swapped out the code and made changes.
😉
@Starcloudsea, do you consider completing the question?
Oh, I'm sorry. I forgot.