BartoszCichecki / LenovoLegionToolkit

Lightweight Lenovo Vantage and Hotkeys replacement for Lenovo Legion laptops.
GNU General Public License v3.0
5.13k stars 232 forks source link

[BUG]: After disabling Lenovo Hotkeys, the Fn notification bar from Tookit does not display properly #557

Closed Jony-Gays closed 1 year ago

Jony-Gays commented 1 year ago

Version

2.9.1

OS

Windows 11 22H2

Device

Lenovo Legion R7000P2020H

BIOS version

LENOVO FSCN26WW, 22/9/9

What's wrong?

After disabling Lenovo Hotkeys, the Fn notification bar from Tookit does not display properly Now, I will describe the problem exactly This is actually a very simple problem, first of all, when I enable Lenovo Hotkeys, and I try to use Fn+F* to open or close the microphone or touchpad, there will be the following notification p1e [p1] P1 So far everything is fine.

However when I use the toolkit to disable Lenovo Hotkeys, the Fn shortcut notification becomes [P2]. It's like a black board. At the same time I found the reason for its problem.------

  1. Your default setting is the bottom right corner
  2. The size of the notification box is wrong P2

When I reposition the notification box to the center button, I will see "Notification bar with normal content but severe size problems" [P3] P3

This is all the description of the bug

How to reproduce the bug?

  1. Use the toolkit to disable Lenovo hotkeys,
  2. use the Fn shortcut to switch the touchpad or microphone on or off
  3. Automatic pop-up notifications

What is the behavior that you expected?

Normal size, normal text display centered notification box

Logs

not logs

Do you have Lenovo software installed?

Did you disable any Lenovo software using Lenovo Legion Toolkit?

Additional information

No response

BartoszCichecki commented 1 year ago

I can't reproduce it, but I found a potential bug. If you still can reproduce this bug when 2.10.0 is released please re-open this issue.

875389955 commented 1 year ago

I can't reproduce it, but I found a potential bug. If you still can reproduce this bug when 2.10.0 is released please re-open this issue.

噢噢