![]() It's for laptop LCD to change the real brightness level when Forcelevel is not set.Įxample skin:(Right Click the (i)icon on top right to view the introductions in English) !CommandMeasure "MeasureBacklight" "Backlight-" !CommandMeasure "MeasureBacklight" "Backlight+" !CommandMeasure "MeasureBacklight" "ChangeBacklight x" It will be set to the nearest level in laptop LCD. Set backlight to x percent(between 0 and 100). !CommandMeasure "MeasureBacklight" "SetBacklight x" Removable, :(for laptop to control monitor)When external monitor is hot pluged, with this option, monitors will be able to reinitialized after 3s to avoid the crash of the rainmeter, the time to reinitialize is according to Update in skin or Bang.Not suggested when you don't hot plug the monitor.įor example:For laptop,SetBacklight 50 may return real brightness 52, but when Policy=Forcelevel, the brightness will be set to 52,and return 50.ĭecide the number of level when using "Backlight+" or "Backlight-".If it's set 20, then change the brightness by 5%.įor laptop LCD it's decide by the OEM in drivers, or you can use Policy=Forcelevel to make the number seems better, but the real level won't change.ġ :Show screen information in the log,the real brightness level for laptop LCD, or the list of the monitors in control.It's no need to be set in daily use. 1 :Default.This Plugin will try to control laptop LCD first in Initialize function, if failed, then the desktop one.Ġ :Try to control all of the desktop monitors(3 at most).It can also be used for laptop to control external monitor.ġ :Control the first desktop monitor.(The number is according to the log when Showlog=1)Ģ :Control the second desktop monitor.For a laptop,the first external monitor should be 2.įorcelevel, :(for laptop)return the nearest brightness according to Divide= It returns the percentage (0-100) of current brightness. I don't know how to solve these problems, hoping some can help improve it. In my test, laptop can only control the external monitor when mode is "copy",and it doesn't works well in some laptop(notebook) computer. It's designed to control 3 monitors at most at the same time, but I've no hardware to test it and it may not work in some situation. It seems most of the monitors since 2006 support it,but you may need to enable it in monitor OSD. To control a desktop monitor (external monitor) ,the monitor must support DDC/CI. It controls the laptop LCD backlight by setting AC/DC brightness in Power Management (IOCTL). This Plugin is used to control the backlight of laptop LCD or desktop monitor.(Support Vista and later) I've wasted lots of time using a desktop monitor control API to control laptop LCD,finally I decide to write them together. I haven't seen it before I write the plugin ,and if you only control the backlight of laptop,the upper one may be better. ![]() But, like I said, I think it was Cacheman.There is already a screen brightness plugin: I'm going to run OHM and the plugin all day today, so I'll know for sure if it causes crashes. ![]() I also noticed I'd get CRC errors when allowing Cacheman to manage memory.Īnyway, I ran OHM and the Rainmeter plugin for a couple hours yesterday without problems (save one: Rainmeter crashed once when refeshing a skin I'm building - don't know if this is OHM related). Windows 7 does a good job of managing memory, as does Cacheman, but if it causes crashes there are problems. At this point, I think it was Cacheman causing the BSOD. But in theses cases you will get a notification from the Open Hardware Monitor itself and it will try to exit safely. There are also some rare cases where the Open Hardware Monitor crashes (well it is more like it doesn't even start). Normal crashs (without blue screen) can happen with any application. I am not sure what Cacheman does internally, but for some of the more advanced things like managing cache it could be using a kernel driver as well (which could cause directly blue screens). The Open Hardware Monitor uses a kernel driver, so it could cause blue screens by itself in theory (but I don't have evidence of any case where it does). If for example the RAM does not run stable then anything can cause indirectly a blue screen. ![]() Mmoeller wrote:I think it is not possible for the rainmeter plugin to directly cause a blue screen if your operating system, hardware (mainly RAM) and all drivers run stable. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |