Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Sign in to follow this  
gir489

Problem with using child window that has HWND_TOPMOST

Recommended Posts

I got tired of the garbage start menu in Windows 10 around a month ago, and wanted to try something else. I remembered StartIsBack from my Windows 8 days, because of the hideous metro (SIB made Win8 useable).

Anyway, I installed StartIsBack++ 1.3.4 like 3 weeks ago, and it was fine, until the Anniversary Update. After the AU, processes that create windows using HWND_TOPMOST when calling SetWindowPos on the process, will not show the taskbar anymore when I ALT+TAB. However, if I change it to HWND_TOP, it "works" normally, and the start menu shows, however my process suffers a problem where my layer may or may not always be on the top, and it always needs to be at the 0th Z index. Because there's no way to manually set the Z-index for an HWND in Windows, I have to rely on TOPMOST to do my job for me.

EDIT: I found that if I hit the Windows key, the taskbar comes up. It's an OK workaround for now, however I usually have my Windows key disabled, because I always hit it by accident.

Edited by gir489

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×