Windows 10: [Win32 API] Resizing a borderless window?

Windows Category - All · Aug 13, 2020

I was trying to implement a borderless window that can be scaled by handling WM_NCHITTEST message. This works now, but whenever I put another window in front, this "borderless" window gets a thick white border. The window style includes WS_THICKFRAME, which is required to make window resizable, and when the window is upfront does not impose any issues. Without WS_THICKFRAME, borderless windows will not get that white border when in the background, but I cannot do the resizing either.

This white border is acceptable if the window is actually a rectangle, but it makes sense to and I was trying to use DwmEnableBlurBehind and make parts of the window transparent. It also makes sense to use SetWindowRgn to make the mouse able to pass through the window if transparent to select something behind the window. When combined, the white border loses its straight outline and turn into something like paint stain which is not acceptable.

Screenshots:

Opaque In Front:

https://forum.nepfan.club/assets/files/2020-08-13/1597297619-251674-normal-noborder.png

Opaque In Back:

https://forum.nepfan.club/assets/files/2020-08-13/1597297658-879297-normal-border.png

Transparent In Front

https://forum.nepfan.club/assets/files/2020-08-13/1597297685-779274-transparent-noborder.png

Transparent In Back

https://forum.nepfan.club/assets/files/2020-08-13/1597297707-526121-transparent-border.png

Region with transparent

https://forum.nepfan.club/assets/files/2020-08-13/1597297867-838043-region-border.png

Cursor selection prtscr did not record the position of cursor, it's at the lens button

https://forum.nepfan.club/assets/files/2020-08-13/1597297755-976067-2020-08-13.png

:)

Brink · Aug 13, 2020

Microsoft filling in divide between Win32 apps and new Windows APIs

Many new and sought-after Windows APIs and features such as BackgroundTasks, Notifications, LiveTiles, Share and more, are either not available or not easily callable from non-packaged Win32 applications. This is due to the programming model for UWP APIs that integrate with the system and have a dependency on the following concepts:

Identity – The need for package or application identity to identify the caller, and an identifier to scope data and resources.

Registration – The need for configuration of machine state during application deployment, which is required by the API and indexed by the package or application identity.

For packaged applications, Identity declared in the Appxmanifest.xml, and Registration is handled by the MSIX deployment pipeline based on the information in the AppxManifest.xml. This allows a simplified calling pattern for UWP APIs where the application code just uses an API. Compare this to a typical Win32 API that requires a register-use-unregister pattern for managing a callback.

We’ve heard your feedback, and in response we’re filling in the divide between Win32 apps and new Windows APIs & features so that you can take advantage of these new APIs & features and enhance your applications. As of Windows Build 10.0.19000.0 we’re introducing the following new AppModel concepts to provide your Win32 app with deeper integration into the OS:

Sparse Package registration
Signed MSIX packages can be installed on Windows today but all content referenced in the package’s Appxmanifest.xml must be present inside the package. A ‘Sparse’ Package contains an AppxManifest.xml but unlike a regular/full package, the manifest can reference files outside its package in a predetermined ‘external location’. This allows applications that are not yet able to adopt complete MSIX packaging to gain Identity, configure state (Registration) as required by UWP APIs and then take advantage of these APIs.

Package ‘External Location’
To support a Sparse Package, a package definition now has a new <allowExternalContent> element. This is what allows your package AppxManifest.xml to reference content outside its package, in a specific location on disk. For example, if your existing Win32 app installs content in C:\Program Files\MyWin32App\ , you can create a Sparse Package that declares the <allowExternalContent> element and during app installation or first run of your app, you can register the Sparse Package and declare C:\Program Files\MyWin32App\ as the external location your app will be using. This way you can continue deploying all your other app artifacts in the locations you do today while taking advantage of the Sparse Package.

Win32 type RuntimeBehavior
To help with compatibility of your existing Win32 app when using a Sparse Package, the app can register to have its application process be run like a non-packaged Win32 app as much as possible. This differs from a fully packaged Win32 app in that it is not subject to filesystem + registry virtualization, lifetime management by the system and other runtime attributes of fully packaged applications. The main runtime similarity between such an app and a fully packaged app is the presence of app/package identity in the running process.

Activation via CreateProcess
The activation path for UWP applications today ensures the app has PackageIdentity in its process token. This is used by UWP APIs to identify the caller and refer to later – either to perform a callback or to look up state that was configured during deployment. Because of this requirement, calling CreateProcess() on a UWP exe will fail as the CreateProcess() pipeline was not enlightened about Identity. In order to support Sparse Packages with an External Location, we leverage the classic Win32 application.manifest to provide Identity in CreateProcess() scenarios.

At their core, these features are about providing a foundation for non-packaged Win32 processes to use our latest APIs and features.

*Please note that these are still new and somewhat advanced development features that do not yet have full Visual Studio integration i.e. there are still some gaps in the end to end authoring experience such as having to create a Sparse Package outside of Visual Studio...
Click to expand...

Read more: Identity, Registration and Activation of Non-packaged Win32 Apps - Windows Developer Blog

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

John Vil · Aug 13, 2020

moving and resizing

Hi Bob,

There may be several reasons why you are unable to resize or move applications after installing an update. To better assist you with your concern, we would like you to answer the questions below:

Does it happen only on one application?

Which application are you having issues resizing or moving?

In the meantime, we suggest you to run the Windows 10 troubleshooter. Kindly follow the steps below:

Press Windows key +X, select
Control panel

Change the view by option on the top right to
Large icons

Click on troubleshooting and click on the
view all option on the left panel

Run the Windows Store apps troubleshooter

Let us know how it goes.

Alec§taar · Aug 13, 2020

WMPlayer win32 error

Ok here's my problem... I try to use windows media player and I get blah blah blah, not a valid Win32 application error. So I try to install wmplayer 10 AND 11 and get the same errors on trying to install it... anyone know of a way to fix these errors??? I've been looking for hours now and can't seem to get a definitive answer *Confused
Click to expand...

List the EXACT "blah, blah" you mention, here please... for ALL installation cases!

(Sound like a possible "DLL-Hell" issue, but "Windows File Protection" &/or "System File Protection" should have countered for this... no biggie, there's ways around that too!)

*Smile

* I have to 'step-out' now, but imo, this is the track to pursue here, & we will when I get back... so, please list that data I request!

APK

Windows 10: [Win32 API] Resizing a borderless window?

[Win32 API] Resizing a borderless window?

[Win32 API] Resizing a borderless window?

[Win32 API] Resizing a borderless window?

[Win32 API] Resizing a borderless window? - Similar Threads - Win32 API Resizing

How to get the latest DPI of System with win32 API.

How to get the latest DPI of System with win32 API.

How to get the latest DPI of System with win32 API.

VSync in Borderless Windowed NOT working

Microsoft Making Win32 APIs More Accessible to More Languages

Borderless PRINTING

Borderless printing

Can Windows Defender detect external win32/kernel api calls?

Microsoft filling in divide between Win32 apps and new Windows APIs

Users found this page by searching for:

borderless Api win32