(Also, I am talking about desktop application. (So, not removing YB for capturing other application windows.) cause you can fetch data from your application as you can like and "steal" user data that user already is entering in same application. In this situation security reason is not applicable. You are capturing you own application window. I am talking about removing YB primary in this scenario. but I would accept your answer if was like this: Currently, there is no possible way to remove YB. It seems this IGraphicsCaptureSession3 & IsBorderRequired interface is really fresh in terms of Window versions. Windows 10 Insider Preview Build 21390 (May 2021) and more. I suppose IsBorderRequired is fully accessible at preview builds like: SDK 20348 offered from VisualStudio is newer than my current Windows 10. ![]() M_session.IsBorderRequired(false) methode. Winrt::Windows::Graphics::Capture::GraphicsCaptureSession m_session there is no IGraphicsCaptureSession3 defined. Maybe exeption is because I had some code mismanagement.īut, previously, I had pushed capture code to C++ level because I had some memory issues using C# version (memory was bubbling for C# version). System.PlatformNotSupportedException: 'Marshalling as IInspectable is not supported in the. I have tried your solution and had some problems.Īs my project is Net6 based, C# definition of IGraphicsCaptureSession3 as InterfaceIsIInspectable is crashing like. (Though, GDI BitBlt can capture window alpha transparently but only for Win32 DC rendered windows, not for WPF & others). It is fast, can produce animated chains like: Window live content -> DirectX (2D/3D) HLSL custom effect -> DirectCompostition or Visual layer.Īfter 10 years, finally one can see some progress! :D Very nice thing is that window -ing preserves alpha transparency and avoids obscurities, where other capturing methods does not! Is there a way to remove "Yellow Boarder Capture Indicator" for desktop application?Īt least, to remove “Yellow border indicator” for case: Desktop app & self-Process created & visible window? ![]() Nor is BitmapCacheBrush because dose not capture window to bitmaps.(and is WPF specific) because output is not exact, capture performance is bad and is WPF specific. Also, in my scenario, RenderTargetBitmap is also not an option. User being informed, why force all other "good" desktop applications not to be able use without "Yellow border"?)Īs I can see, you can remove “Yellow border” only in case for in-application window & window is DWM-DWMWA_CLOAK.īut, my scenario demands not to do DWM-DWMWA_CLOAK. So UWP security is not in consideration for desktop app! (At desktop, if "malign" desktop app can get information from screen without Where “Yellow Boarder Capture Indicator” does not show up (Thanks God!). In desktop environment there are more ways to capture from screen (using DXGI OutputDuplication or GDI BitBlt), I suppose this is because UWP security, for to inform user something is being captured.īut, my application is desktop based (WPF, Win32, DirectX). When capturing of a window starts, “Yellow Boarder Capture Indicator” shows up like at this image:
0 Comments
Leave a Reply. |