search

2009-Nissan-Cube / About-This-Hack

Discover your hardware on macOS with this simple, user-friendly hardware info app that retains the beloved design language of the classic 'About This Mac' interface, while gaining access to a wealth of additional features.
MIT License
290 stars 23 forks source link

Displays an incorrect display configuration #99

Closed Fischmuetze closed 4 months ago

Fischmuetze commented 5 months ago

This is the real config true

The configuration displayed by the app false

0xCUB3 commented 5 months ago

Thanks for bringing this up. Unfortunately, there's no way (that I know of) to pull the exact display configuration (I'm assuming that's what you are referring to - where the monitors are placed with respect to each other), so I don't think this is a fixable issue. Perhaps @matxpa played around with this in his fork, but I wouldn't keep my fingers crossed.

On the other hand, it looks like the middle text stretches out too wide! Something else to fix for the next bug fix release :)

Fischmuetze commented 5 months ago

Hi, thank you for the quick response. I don't mean the arrangement of the monitors. I mean ether more the description (name) of the monitors and their allocated resolution data. As you can see I have a built-in Retina display with high res (3024x1964) and 2x Dell monitors (2560x1440). But "About-This-Hack" mixed that wrong and shows the resolution data of the MacBook Pro built-in Retina display as "Color display" and for the built-in Retina display the resolution data of the Dell monitor. Also the name of the second monitor isn't displayed as Dell (instead it shows Color LCD.

Maybe just as hint - This app project is able to show my configuration correct https://github.com/MonitorControl/MonitorControl

0xCUB3 commented 5 months ago

I'll look into monitorcontrol's method. For some reason, displays are weird in that apple randomly renames them sometimes in the "System Information" app (which is where we basically pull our data from). At this point, I'm not sure there's a way around it, but if MonitorControl can do it, we might be able to do it too.