If you move your cursor above a gadget you can drag it around your desktop. It doesn't need to stay on the sidebar. There will also appear some buttons next to the gadget. Click on the X to close a gadget or on the wrench icon to access its options.
The next gadget is a clipboard manager. Here I copied the installer file and then the name of the file. Clipboarder will display everything you copy to the clipboard. By clicking on an element you make it the current clipboard. This way you can select older clipboards and paste them into other applications. You can also open a clipboard directly.
Here you can, for example, click on the first checkbox to make the sidebar always visible. This way you have your gadgets always in sight. A disadvantage is though, that the close button of maximized windows isn't on the top-right corner anymore. To fix this you can put the sidebar on the left side.
This way you can keep track of some applications on the side. You can hover with your cursor over the preview to peek into the window, just like in the taskbar. Right-clicking on the preview gives you some options as well.
Window Blinds crash over and over and over again for the entire time a progress bar is showing.The crashes happen so rapidly that I cannot disable window blinds ..
If I am lucky I can cancel what ever process the progress bar is about ... unloading window blinds allows me operate normally.Also window blinds does not crash if only one window is active when a progress bar starts.It only seems to occur if you have multiple windows open or attempt to open a second window during the progress bar motion.
I am running on 4K Monitor too. I don't have crash issues on progressbar. Please try purge and reinstall steps as mentioned here: -support-faq#reinstalling Just make sure to redownload the latest version from your account. Reboot after the purged. Reinstall, and Reboot again after the installation. Retest it. Report back here.
That crash is shown as a dll unloaded situation which should not happen when WindowBlinds is running as the dll would remain in process. This would suggest something is forcing the dll to be removed from memory.
4a15465005