ModernFlyouts: Broken "Brightness" Flyout in 0.10.0.0 version : showing incorrect data

ModernFlyouts Version

0.10.0.0

Windows version

Windows 10 22H2

OS build

No response

Platform

x64

Area(s) with issue?

General

Steps to reproduce

in version 0.9.3 there is a problem with Keyboard Input Flyout appearing on Audio change according to comments in “issues” chapter, this is fixed in ver 0.10.0.0 I can confirm thats true, but instead in ver 0.10.0.0 there exists another bug

Steps to reproduce :

  • Enable “Brightness” flyout
  • change brightness using default laptop keys
  • now, compared to the ver 0.9.3 the Flyout shows maximum level of brightess as 66%, and showing the label of brightness “Generic PnP Monitor”. In ver 0.9.3 the Brightness Flyout was clean, had no lables and the scale was from 1% to 100%, just like Audio Flyout.

please fix that

✔️ Expected Behavior

Brightness Flyout reflects changes in accurate way, similar to Audio changes, from 1% to 100% presented on the Flyout, just like in ver 0.9.3

❌ Actual Behavior

in ver 0.10.0.0 The Flyout is limited to 66% and not showing any changes above, also displaying the name of the Display (Generic PnP Monitor), compared to the stable 0.9.3 that was a clean flyout without any labels and having full scale from 1% to 100%

Other Software

No response

Additional Context

No response

About this issue

  • Original URL
  • State: open
  • Created 10 months ago
  • Comments: 27 (17 by maintainers)

Most upvoted comments

@user1888425 Can you send me a screenshot of the brightness flyout while it shows on screen as that will be a huge help?

@user1888425 The old way was quite different and used .NET capabilities. The new way is using Microsoft’s api’s from inside dll’s. However, the old way doesn’t work for me but the new way does. For you guys, it’s the other way around.

hi there, thanks for clarifying how the old and new approach are different in its nature. I believe your suggestion about some kind of “compatibility mode” switcher might be a very elegant and clean solution

thanks for your reply

let me add more context into my report

in ver 0.10.00 I m able to enable the Brightness Flyout. when enabled, the Brighness section into the app looks like that : image

I can change brightness using default buttons, and also by moving the slider of the flyout.

But the main issue is that by using slider Im limited to 66%, and I still can go beyond 66% using Laptop Brightness Keys, but the Flyout just keep showing 66% as a maximum level. It also now has some counter badge at this flyout, as if it counts the number of attached displays. The problem is that I dont have any displays attached.

those things I mentions were different in 0.9.3 and worked much better and without additional visual bothering information. Ver 0.9.3 was much cleaner in visual aspect and better in technical aspect of Brighness Flyout

UPD :

66% in Flyout is not just graphical representation of 100%, like if 66 = 100 If I set my global Brightness at 100, and then move the slider of the Flyout from 66 to 60, the global Brightness reverts to 60