I work with 2 screens, and usually 3 or more open windows visible. At times, I don't know which one has focus. When I want to make sure a window has focus, I go to the taskbar 

and click that task. Unfortunately, if that window already has focus, it
gets minimized. Not what I want, ever.

I would like an option that always gives focus to the task I click.

Updated to 5.5 after daily requests to do so. After updating, my taskbar icons are tiny. w10_large_icons is still set to 1, but the option is no longer working. Please fix -- this is the only reason i'm using the tweaker

I drag my tabs into the order I choose. I pop up the tab menu by hovering over the FF taskbar icon. I find them often lately all scrambled again.

I use MySessions as a FF Add-on. Perhaps this the guilty party?

I don't know if you have ever used the RemoteApp feature of remote desktop; it seamlessly streams windows from a host into the desktop of a client, and the windows show up on the client machine's taskbar, along with their tray icons, mixed in with the locally running applications as though everything was local.

The feature runs windows in its own WinSta and session and does not use Explorer.exe since it does not stream the taskbar or desktop, only the applications.

in fact, the host uses a process called rdpshell.exe as the desktop invironment: 

At one point while I was messing around with the process I was able to get it to stream a taskbar that would work on the remote machine along with the local taskbar. this also gave me a start menu, and was very handy.

I don't know why Microsoft does not officially support this use case, but I know its possible and would likely involve some of the methods you use for your tweaker. (Is there source code available anywhere btw?) 

Could you look into incorporating this into 7+tbt ?

All functions fail.

MessageBox: Not inject in explorer

This just started happening a few minutes ago.  I updated to 7TT 5.5 a couple days ago. 

Without providing any stimulus to the task bar, all of a sudden my windows on the taskbar just rearranged themselves.  The order of all buttons within groups were preserved, but two groups just magically rearranged themselves to an order I've never set them to.  My mouse cursor was nowhere near the taskbar when this happened.

After I moved the groups back to the order they were in before, they rearranged themselves again seconds later to the way they were before I restored their original order the first time.

There must be other conditions involved here, because it's not doing it anymore.  It did it like three times in a row within seconds of each other.  After that, I force-closed 7TT from Task Manager and re-opened it.  After I re-opened it, the main 7TT window was acting weird.  It would disappear for a split-second and immediately reappear.  It did that a few times as well, spaced a couple seconds apart each time.

My taskbar is oriented vertically.  I'm using 10 Pro 1709.  This is the only program exhibiting strange behavior.  I don't really know how to quantify this any better at the moment.  Are there logs somewhere?  I can't find any in ...\Appdata\Roaming.

I can only fit 19 apps in each taskbar row.  After that Windows adds another row and has up/down arrows on the right side I can use to scroll between rows.  Dragging apps around inside a row works great, but I can't figure out how to drag them between rows.  It would be nice if I could drag them to the up or down arrow, hover there while it goes up/down through the rows (either variable speed or maybe 2 per second), then drag & drop it where I want inside the row.  Thank you.

If the file explorer is the first item in the taskbar, it is moved to the last position every time the 7+tt is launched/closed. If the file explorer is the second or third item (or any other position), this issue does not happen.

e.g. I have:

    explorer | edge | excel | word

I launch 7+tt or close 7+tt or change 'Combining' settings or use taskbar inspector:

    edge | excel | word | explorer

I started using your app a few versions ago and this issue has always happened.