Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show desktop can't be clicked on the extreme bottom-right pixel #717

Closed
Falki-git opened this issue Jul 3, 2021 · 21 comments
Closed

Show desktop can't be clicked on the extreme bottom-right pixel #717

Falki-git opened this issue Jul 3, 2021 · 21 comments

Comments

@Falki-git
Copy link

Describe the bug
When you move your mouse to the very bottom-right corner (last pixel) show desktop button can't be clicked. This is very important for quickly clicking on the button as you can just flick your mouse down-right without "aiming" at the button

To Reproduce
Steps to reproduce the behavior:

  1. Move your mouse completely down and right
  2. Try clicking, nothing happens
  3. Move your mouse 1 pixel up or left - it now works

Expected behavior
The bottom-right pixel also hovers the show desktop button

Desktop (please complete the following information):

  • OS: Windows 10 Pro
  • Version: 2004

Additional context
Tried the latest release 1.7.0.0 as well as the pre-release 1.7.1.0 - problem persists

@moxwel
Copy link

moxwel commented Jul 4, 2021

Can confirm this problem persists.

When clicking the "Show Desktop" at the very bottom pixel, it doesn't work.
problem

It's kind of annoying, I use that button a lot.

However, this problem doesn't happen with the Start Menu button.
problem2

Maybe this issue is related to #716 ?

@luisconceicao1
Copy link

I'm having the same issue here :/ I lost a few hours trying to solve it but didn't work. 😢

  • could you please fix it? I like so much the TaskBarX I'm missing it a lot :(

@luisconceicao1
Copy link

As issue #716 it is the same as me.

@sleepnov4
Copy link

sleepnov4 commented Jul 6, 2021

Yes, this case is the same as mine. You should remove this case because this is a duplicated issue. You also can forward or send your issue to my problem case. Please read #108 .

@sleepnov4
Copy link

I did some research about your issue and this issue already got fixed. Someone already report this kind of issue (#682). Maybe you can use the Pre-release version 1.7.1.0. You can download it from here.

@moxwel
Copy link

moxwel commented Jul 6, 2021

I did some research about your issue and this issue already got fixed. Someone already report this kind of issue (#682). Maybe you can use the Pre-release version 1.7.1.0. You can download it from here.

@sleepnov4 The issue about the "Show Desktop" button persists on version 1.7.1.0.

@Falki-git
Copy link
Author

I did some research about your issue and this issue already got fixed. Someone already report this kind of issue (#682). Maybe you can use the Pre-release version 1.7.1.0. You can download it from here.

No, this issue isn't the same as #682, although the root cause is probably the same.

As I stated in the description of this issue, I already tested 1.7.1.0 and the issue isn't resolved. 1.7.1.0 resolves that the task bar is moved all the way to the bottom, so you can now click taskbar items while hovering the mouse on the last bottom pixel of the item. However, this show desktop button issue is still affected for the bottom-right pixel of the show desktop button.

@The-Dark-Matter
Copy link

The-Dark-Matter commented Jul 8, 2021

I have the same problem and I only see 1 pixel now working. I screenshoted it and got this. That blue color is my wallpaper and I only see it in that pixel.

imagen_2021-07-08_170434

@flylogs
Copy link

flylogs commented Jul 15, 2021

Use Windows+D, faster, does the same.

@matinkg
Copy link

matinkg commented Jul 19, 2021

I confirm this problem on version 1.7.1.0.

I fixed that by following these steps:

  1. Uninstall TaskbarX version 1.7.1.0 through TaskbarX Configurator.exe
  2. Remove all the files related to TaskbarX version 1.7.1.0
  3. Lock the taskbar by right-clicking on it
  4. Restart the pc
  5. Install TaskbarX version 1.6.9.0

I don't know if the problem was with the new version or with the unlocked taskbar. But after locking the taskbar and downgrade to version 1.6.9.0 the problem was gone.
One more thing, after disabling TaskbarX version 1.7.1.0 the problem still exist until next reboot. So at step 4 I restarted the pc to fix that.

@stiffbruno
Copy link

I confirm this issue, and as stated above, the problem don't exist in version 1.6.9.0.

@Double-A-92
Copy link

Can confirm that this issue is still present in version 1.7.2.0.

The bottom right pixel is even visually missing from the taskbar.

In general it seems like the bottom-right most pixel of the whole screen is not active. E.g. this issue also happens if you have a vertical task bar on the right side of your screen.

@Falki-git
Copy link
Author

Issue still persists in 1.7.2.0

@ChrisAnd1998
Copy link
Owner

To be able to focus on major/current bugs I had to close all issues. The issues section has gotten very messy to a point that I couldn't follow it anymore. Most issues are duplicates, very old or are already fixed/solved. Feel free to reopen this issue if you still have this issue on the latest version of TaskbarX to get my attention. All feature requests have been put in a list here: 💡| Feature requests #870

I hope you understand ❤️

@Double-A-92
Copy link

Double-A-92 commented Dec 25, 2021

I just tested it, and this still happens in the newest version (1.7.4.0).
Is there a way to reopen this issue here, so the information in the thread doesn't get lost?

@ChrisAnd1998
Copy link
Owner

I confirm this happens for me too. Now I will find out what is causing this to happen ;)

@ChrisAnd1998
Copy link
Owner

ChrisAnd1998 commented Dec 25, 2021

Should be fixed now. Make sure to restart Explorer.exe or just restart your PC before trying.
https://github.com/ChrisAnd1998/TaskbarX/releases/tag/1.7.5.0

@goyalyashpal
Copy link
Contributor

  • can u share the fixing commit??
  • and if it's confirmed that it's fixed, then shouldnt this issue be closed?
  • if the confirmation is awaited, then that should be mentioned in last comment or via a label indicating that (smth like "waiting on response/input" etc...)

@ChrisAnd1998
Copy link
Owner

ChrisAnd1998 commented Dec 25, 2021

@yashpalgoyal1304 I have added a label "Awaiting confirmation" now. The issue will be closed when confirmed indeed. Normally i don't do commits but if you really want it i will when the issue is confirmed fixed ;)

@goyalyashpal
Copy link
Contributor

awesome (:

ChrisAnd1998 added a commit that referenced this issue Dec 26, 2021
@Double-A-92
Copy link

This fixed it for me. Thanks for the quick work. :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests