rainmeter - Project Hosting on Google Code

Last 7 days Jan 03, 2010 issue 126 ("Unable to create font" error) commented on by alkonman - I believe this is the error I get upon satart after install. dried the zip and the download .exe both with same unusable install, app just shows fine lines on screen, any ideas. did not find help in forums through search. Using Win7Pro I believe this is the error I get upon satart after install. dried the zip and the download .exe both with same unusable install, app just shows fine lines on screen, any ideas. did not find help in forums through search. Using Win7Pro Jan 03, 2010 issue 128 (GCal Reader displays recurring events before regular events) commented on by i...@fortpride.org - This bug has been driving me CRAZY! Thank you SO much, Dirk. Gary Rechnitz Colorado This bug has been driving me CRAZY! Thank you SO much, Dirk. Gary Rechnitz Colorado Jan 02, 2010 issue 111 (Dragging skins to new locations is now broken...) commented on by fathead.b - How can i fix it in ver 1.1? How can i fix it in ver 1.1? Jan 01, 2010 issue 55 (High CPU usage) commented on by ikjadoon - Yeeaaaaahh! :D Yeeaaaaahh! :D Dec 31, 2009 issue 135 (Zune Plugin) commented on by smartfxs...@hotmail.com - Second that..... Second that..... Dec 31, 2009 issue 132 (Download=1 overwrites duplicate filenames.) changed by kenz0.sanada - spx and I started developing for the solution of this problem. Status: Started Owner: kenz0.sanada spx and I started developing for the solution of this problem. Status: Started Owner: kenz0.sanada Dec 31, 2009 issue 137 (Any mouse action go through the meter and affects the meter ...) Status changed by kenz0.sanada - Status: Started Status: Started Dec 31, 2009 issue 137 (Any mouse action go through the meter and affects the meter ...) Status changed by kenz0.sanada - Status: Accepted Status: Accepted Dec 31, 2009 issue 136 (unable to locate rainmeter.ini) Status changed by kenz0.sanada - Status: Invalid Status: Invalid Dec 31, 2009 issue 128 (GCal Reader displays recurring events before regular events) Status changed by kenz0.sanada - Status: Invalid Status: Invalid Dec 31, 2009 issue 120 (Limit on using MeterStyle= in a skin if the [MeterStyle] is ...) changed by kenz0.sanada - Status: Done Owner: --- Labels: Type-Other −Type-Defect Status: Done Owner: --- Labels: Type-Other −Type-Defect Dec 31, 2009 issue 87 (Webparser doesn't update the downloaded file) changed by kenz0.sanada - Status: Started Owner: kenz0.sanada Status: Started Owner: kenz0.sanada Dec 31, 2009 issue 85 (WebParsr.dll "hangs" when skin refreshed repeatedly) Owner changed by kenz0.sanada - Owner: --- Owner: --- Dec 31, 2009 issue 85 (WebParsr.dll "hangs" when skin refreshed repeatedly) Status changed by kenz0.sanada - Status: Done Status: Done Dec 31, 2009 issue 81 (Rainmeter causing "system" process to tax cpu) changed by kenz0.sanada - Status: Done Labels: Type-Other −Type-Defect Status: Done Labels: Type-Other −Type-Defect Dec 31, 2009 issue 69 (New Default Skin to be packaged with next full release!?!!) changed by kenz0.sanada - Status: Done Owner: --- Status: Done Owner: --- Dec 31, 2009 issue 61 (Object Position Issues on Multiple Monitor Displays) Status changed by kenz0.sanada - Status: Accepted Status: Accepted Dec 31, 2009 issue 60 (prevent res changes (ex. when playing a game) from skewing l...) Status changed by kenz0.sanada - Status: Done Status: Done Dec 31, 2009 issue 55 (High CPU usage) Status changed by kenz0.sanada - Status: Done Status: Done Dec 31, 2009 issue 52 (Update Context Menu w/out refreshing all) Status changed by kenz0.sanada - Status: WontFix Status: WontFix Dec 31, 2009 issue 42 (Wine can't load rainmter c runtime library.) changed by kenz0.sanada - Status: WontFix Labels: Type-Other −Type-Enhancement Status: WontFix Labels: Type-Other −Type-Enhancement Dec 31, 2009 issue 38 (ToolTips) Labels changed by kenz0.sanada - Labels: Component-Logic Labels: Component-Logic Dec 31, 2009 issue 36 (Problem With VCredistributable Installer) Status changed by kenz0.sanada - Status: Done Status: Done Dec 31, 2009 issue 13 (Extend Webparser download method) changed by kenz0.sanada - Status: Started Owner: kenz0.sanada Status: Started Owner: kenz0.sanada Dec 31, 2009 issue 11 (New options for STRINGs) Status changed by kenz0.sanada - Status: Done Status: Done Dec 31, 2009 issue 75 (Using a weather skin and it is not working? Weather.com Pull...) Status changed by kenz0.sanada - Status: Done Status: Done Last 30 days Dec 24, 2009 issue 5 (Support Regular Expressions for substitute) commented on by robarriosg - I'm actually really interested in this feature, specially the use it could have with Winamp and other players. I'm actually really interested in this feature, specially the use it could have with Winamp and other players. Dec 22, 2009 issue 81 (Rainmeter causing "system" process to tax cpu) commented on by darrenjcook - Thanks, I'm at the latest broadcom drivers :( Might be time for a new card anyway. Thanks, I'm at the latest broadcom drivers :( Might be time for a new card anyway. Dec 21, 2009 issue 128 (GCal Reader displays recurring events before regular events) Labels changed by jsmorley - Labels: Type-Other Priority-Low −Type-Defect −Priority-Medium Labels: Type-Other Priority-Low −Type-Defect −Priority-Medium Dec 21, 2009 issue 127 (Need a bang to do a "Refresh All" from the command line) Status changed by jsmorley - Status: Fixed Status: Fixed Dec 21, 2009 issue 133 (Support For Visual Basic?) Labels changed by jsmorley - Labels: Type-Enhancement Priority-Low −Type-Defect −Priority-Medium Labels: Type-Enhancement Priority-Low −Type-Defect −Priority-Medium Dec 21, 2009 issue 136 (unable to locate rainmeter.ini) Labels changed by jsmorley - Labels: Type-Other Priority-Low −Type-Defect −Priority-Medium Labels: Type-Other Priority-Low −Type-Defect −Priority-Medium Dec 21, 2009 issue 135 (Zune Plugin) Labels changed by jsmorley - Labels: Type-Enhancement Priority-Low −Type-Defect −Priority-Medium Labels: Type-Enhancement Priority-Low −Type-Defect −Priority-Medium Dec 19, 2009 issue 81 (Rainmeter causing "system" process to tax cpu) commented on by darren.carter - I had the exact same problem. My resolution was to upgrade my network card drivers. I rebooted (even though it didn't require me to) and my CPU load decreased to normal levels. Hope this helps! I had the exact same problem. My resolution was to upgrade my network card drivers. I rebooted (even though it didn't require me to) and my CPU load decreased to normal levels. Hope this helps! Dec 19, 2009 issue 126 ("Unable to create font" error) commented on by kenz0.sanada - Yes, you are right. Actually, the direct cause that shows the error is not "DynamicVariables". The reason for the direct cause is that FontSize is 0. When using Calc, even if it defines the value fixed like "Formula=20", Calc certainly returns 0 once at the time of loading of a skin. In order to try dynamic font size, there is no method except using "DynamicVariables", and it is a formula to use Calc for this approach. That is, the occurrence of the error doesn't escape if it tries to change the font size dynamically. The problem which I point out is not about the defect of one function, and it is about the practical trouble by the collision of some functions. I am not sure but I think that it should check off of an error message about FontSize. Because this error doesn't have the meaning so much. Is there on earth a user who defines it by mistake as "FontSize=0"? Yes, you are right. Actually, the direct cause that shows the error is not "DynamicVariables". The reason for the direct cause is that FontSize is 0. When using Calc, even if it defines the value fixed like "Formula=20", Calc certainly returns 0 once at the time of loading of a skin. In order to try dynamic font size, there is no method except using "DynamicVariables", and it is a formula to use Calc for this approach. That is, the occurrence of the error doesn't escape if it tries to change the font size dynamically. The problem which I point out is not about the defect of one function, and it is about the practical trouble by the collision of some functions. I am not sure but I think that it should check off of an error message about FontSize. Because this error doesn't have the meaning so much. Is there on earth a user who defines it by mistake as "FontSize=0"? Dec 19, 2009 issue 126 ("Unable to create font" error) commented on by djmcnz - The combination of using the word "dynamic" and including "DynamicVariables" in you example may unintentionally misdirect readers. The problem exhibts when the variable "FontSize" is not a number. I can't find a relationship between the problem and the "DynamicVariables" parameter. The combination of using the word "dynamic" and including "DynamicVariables" in you example may unintentionally misdirect readers. The problem exhibts when the variable "FontSize" is not a number. I can't find a relationship between the problem and the "DynamicVariables" parameter. Dec 17, 2009 r317 (* Changed the way to get the information of the multiple dis...) committed by spx268 - * Changed the way to get the information of the multiple display monitors. This change brings the order of monitors close to the order of "Display Properties" due to using EnumDisplayDevices and EnumDisplaySettings instead of EnumDisplayMonitors. (If EnumDisplayDevices failed, EnumDisplayMonitors is used as before.) ----- * Added the "Display Monitor" submenu in [Skins Menu]-[Position]. These menus convert the present position to the relative position from the specified monitor. (But the meter window doesn't move to the specified monitor area immediately. Only converts.) - "Use default: Primary monitor" removes the @-directive from WindowX/Y. - @0(@1, @2, ...) adds the specified monitor number to WindowX/Y. @0 means "The Virtual Screen". (http://msdn.microsoft.com/en-us/library/dd145136%28VS.85%29.aspx) - If "Auto-select based on window position" is checked, the WindowX and WindowY "@n" settings are made automatically based on the position of the meter's window. If a monitor is selected directly using "Display Monitor" in the Rainmeter / skin context menu, this menu is unchecked. This setting can be manually made in either the [Rainmeter] (all configs) or individual config sections of Rainmeter.ini. AutoSelectScreen If set to 1, the WindowX and WindowY "@n" settings are made automatically based on the position of the meter's window. If a monitor is selected directly using "Display Monitor" in the Rainmeter / skin context menu, this setting is reset to 0. ----- * Added the variables for multiple display monitors and the virtual screen. All X/Y positions are represented in the virtual screen coordinates. The following variables are for the virtual screen. #VSCREENAREAX# is the X-position of the left-side of the virtual screen. #VSCREENAREAY# is the Y-position of the top-side of the virtual screen. #VSCREENAREAWIDTH# is the width of the virtual screen. #VSCREENAREAHEIGHT# is the height of the virtual screen. The following variables are for the PRESENT monitor. Note that these variables automatically change by the WindowX and WindowY "@n" settings. If "@n" is not set, these variables return the value of the primary monitor. #WORKAREAX# is the X-position of the left-side of the work area. #WORKAREAY# is the Y-position of the top-side of the work area. #WORKAREAWIDTH# is the width of the work area. #WORKAREAHEIGHT# is the height of the work area. #SCREENAREAX# is the X-position of the left-side of the monitor screen. #SCREENAREAY# is the Y-position of the top-side of the monitor screen. #SCREENAREAWIDTH# is the width of the display resolution. #SCREENAREAHEIGHT# is the height of the display resolution. The following variables are for the PRIMARY monitor. #PWORKAREAX# is the X-position of the left-side of the work area. #PWORKAREAY# is the Y-position of the top-side of the work area. #PWORKAREAWIDTH# is the width of the work area. #PWORKAREAHEIGHT# is the height of the work area. #PSCREENAREAX# is the X-position of the left-side of the monitor screen. (maybe, always 0) #PSCREENAREAY# is the Y-position of the top-side of the monitor screen. (maybe, always 0) #PSCREENAREAWIDTH# is the width of the display resolution. #PSCREENAREAHEIGHT# is the height of the display resolution. The following variables are for the SPECIFIED monitor. (@n = @1, @2, ...) #WORKAREAX@n# is the X-position of the left-side of the work area. #WORKAREAY@n# is the Y-position of the top-side of the work area. #WORKAREAWIDTH@n# is the width of the work area. #WORKAREAHEIGHT@n# is the height of the work area. #SCREENAREAX@n# is the X-position of the left-side of the monitor screen. #SCREENAREAY@n# is the Y-position of the top-side of the monitor screen. #SCREENAREAWIDTH@n# is the width of the display resolution. #SCREENAREAHEIGHT@n# is the height of the display resolution. ----- * Other related changes: - Fixed the problem that the primary monitor isn't recognized correctly. - Fixed the problem that the information of the multiple display monitors is refreshed excessively. - For DynamicVariables, when display setting or workarea size has been changed, all variables are now updated to apply changed WORKAREA/SCREENAREA variables. - Fixed the problem that the "On Desktop" window isn't dragged correctly when the top-left corner of the virtual screen has negative coordinates. - Changed the way to stick the "On Desktop" window. ("SysListView32/FolderView" is used instead of "Progman/Program Manager".) ----- * Other changes: - When the meter window is draggable and isn't dragged, LeftMouseUpAction is now executed. - Added MouseDoubleClickAction (LeftMouseDoubleClickAction, RightMouseDoubleClickAction, MiddleMouseDoubleClickAction). If MouseDoubleClickAction is empty when mouse button is double- clicked, MouseDownAction is executed instead. - Fixed the problem that the Meter's hit-test code checks outside the area. - Changed the way to set the #CURRENTCONFIG#. (CMeterWindow::GetSkinName() is now used instead of parsing the path.) * Changed the way to get the information of the multiple display monitors. This change brings the order of monitors close to the order of "Display Properties" due to using EnumDisplayDevices and EnumDisplaySettings instead of EnumDisplayMonitors. (If EnumDisplayDevices failed, EnumDisplayMonitors is used as before.) ----- * Added the "Display Monitor" submenu in [Skins Menu]-[Position]. These menus convert the present position to the relative position from the specified monitor. (But the meter window doesn't move to the specified monitor area immediately. Only converts.) - "Use default: Primary monitor" removes the @-directive from WindowX/Y. - @0(@1, @2, ...) adds the specified monitor number to WindowX/Y. @0 means "The Virtual Screen". (http://msdn.microsoft.com/en-us/library/dd145136%28VS.85%29.aspx) - If "Auto-select based on window position" is checked, the WindowX and WindowY "@n" settings are made automatically based on the position of the meter's window. If a monitor is selected directly using "Display Monitor" in the Rainmeter / skin context menu, this menu is unchecked. This setting can be manually made in either the [Rainmeter] (all configs) or individual config sections of Rainmeter.ini. AutoSelectScreen If set to 1, the WindowX and WindowY "@n" settings are made automatically based on the position of the meter's window. If a monitor is selected directly using "Display Monitor" in the Rainmeter / skin context menu, this setting is reset to 0. ----- * Added the variables for multiple display monitors and the virtual screen. All X/Y positions are represented in the virtual screen coordinates. The following variables are for the virtual screen. #VSCREENAREAX# is the X-position of the left-side of the virtual screen. #VSCREENAREAY# is the Y-position of the top-side of the virtual screen. #VSCREENAREAWIDTH# is the width of the virtual screen. #VSCREENAREAHEIGHT# is the height of the virtual screen. The following variables are for the PRESENT monitor. Note that these variables automatically change by the WindowX and WindowY "@n" settings. If "@n" is not set, these variables return the value of the primary monitor. #WORKAREAX# is the X-position of the left-side of the work area. #WORKAREAY# is the Y-position of the top-side of the work area. #WORKAREAWIDTH# is the width of the work area. #WORKAREAHEIGHT# is the height of the work area. #SCREENAREAX# is the X-position of the left-side of the monitor screen. #SCREENAREAY# is the Y-position of the top-side of the monitor screen. #SCREENAREAWIDTH# is the width of the display resolution. #SCREENAREAHEIGHT# is the height of the display resolution. The following variables are for the PRIMARY monitor. #PWORKAREAX# is the X-position of the left-side of the work area. #PWORKAREAY# is the Y-position of the top-side of the work area. #PWORKAREAWIDTH# is the width of the work area. #PWORKAREAHEIGHT# is the height of the work area. #PSCREENAREAX# is the X-position of the left-side of the monitor screen. (maybe, always 0) #PSCREENAREAY# is the Y-position of the top-side of the monitor screen. (maybe, always 0) #PSCREENAREAWIDTH# is the width of the display resolution. #PSCREENAREAHEIGHT# is the height of the display resolution. The following variables are for the SPECIFIED monitor. (@n = @1, @2, ...) #WORKAREAX@n# is the X-position of the left-side of the work area. #WORKAREAY@n# is the Y-position of the top-side of the work area. #WORKAREAWIDTH@n# is the width of the work area. #WORKAREAHEIGHT@n# is the height of the work area. #SCREENAREAX@n# is the X-position of the left-side of the monitor screen. #SCREENAREAY@n# is the Y-position of the top-side of the monitor screen. #SCREENAREAWIDTH@n# is the width of the display resolution. #SCREENAREAHEIGHT@n# is the height of the display resolution. ----- * Other related changes: - Fixed the problem that the primary monitor isn't recognized correctly. - Fixed the problem that the information of the multiple display monitors is refreshed excessively. - For DynamicVariables, when display setting or workarea size has been changed, all variables are now updated to apply changed WORKAREA/SCREENAREA variables. - Fixed the problem that the "On Desktop" window isn't dragged correctly when the top-left corner of the virtual screen has negative coordinates. - Changed the way to stick the "On Desktop" window. ("SysListView32/FolderView" is used instead of "Progman/Program Manager".) ----- * Other changes: - When the meter window is draggable and isn't dragged, LeftMouseUpAction is now executed. - Added MouseDoubleClickAction (LeftMouseDoubleClickAction, RightMouseDoubleClickAction, MiddleMouseDoubleClickAction). If MouseDoubleClickAction is empty when mouse button is double- clicked, MouseDownAction is executed instead. - Fixed the problem that the Meter's hit-test code checks outside the area. - Changed the way to set the #CURRENTCONFIG#. (CMeterWindow::GetSkinName() is now used instead of parsing the path.) Dec 12, 2009 issue 137 (Any mouse action go through the meter and affects the meter ...) reported by kenz0.sanada - With the case having an overlapping meter, any mouse action go through the meter and affects the meter of the lower layer. It can reproduce a problem in the following easy example. ----------------------------------- [Rainmeter] BackgroundMode=2 SolidColor=FFFFFF BackgroundMargins=10,10,10,10 [Meter-layer1] Meter=IMAGE X=10 Y=10 W=100 H=100 SolidColor=0000FF88 MouseOverAction=!Execute [!RainmeterShowMeter Meter-hover][!RainmeterRedraw] [Meter-hover] Meter=IMAGE X=0r Y=0r W=100 H=100 SolidColor=0000FF Hidden=1 MouseLeaveAction=!Execute [!RainmeterHideMeter Meter-hover][!RainmeterRedraw] LeftMouseDownAction=!Execute [notepad] [Meter-layer2] Meter=IMAGE X=50r Y=50r W=100 H=100 SolidColor=FF0000 LeftMouseDownAction=!Execute [cmd] ----------------------------------- MouseOver/LeaveAction of blue meter will react in the portion with which the center overlapped. In addition, a click action also go through the red meter. In this part, the upper layer action will be ignored and lower layer action will be executed. As for the problem of MouseOver/LeaveAction, also when a separate skin is piled up, it is reproduced. With the case having an overlapping meter, any mouse action go through the meter and affects the meter of the lower layer. It can reproduce a problem in the following easy example. ----------------------------------- [Rainmeter] BackgroundMode=2 SolidColor=FFFFFF BackgroundMargins=10,10,10,10 [Meter-layer1] Meter=IMAGE X=10 Y=10 W=100 H=100 SolidColor=0000FF88 MouseOverAction=!Execute [!RainmeterShowMeter Meter-hover][!RainmeterRedraw] [Meter-hover] Meter=IMAGE X=0r Y=0r W=100 H=100 SolidColor=0000FF Hidden=1 MouseLeaveAction=!Execute [!RainmeterHideMeter Meter-hover][!RainmeterRedraw] LeftMouseDownAction=!Execute [notepad] [Meter-layer2] Meter=IMAGE X=50r Y=50r W=100 H=100 SolidColor=FF0000 LeftMouseDownAction=!Execute [cmd] ----------------------------------- MouseOver/LeaveAction of blue meter will react in the portion with which the center overlapped. In addition, a click action also go through the red meter. In this part, the upper layer action will be ignored and lower layer action will be executed. As for the problem of MouseOver/LeaveAction, also when a separate skin is piled up, it is reproduced. Dec 10, 2009 issue 136 (unable to locate rainmeter.ini) reported by phenom07000 - What steps will reproduce the problem? 1.just installed it 2.ran it 3.got the error What is the expected output? What do you see instead? What version of the product are you using? On what operating system? the one on the home page Please provide any additional information below. If the problem is a related to some config option attaching a example is always a good idea. Try to keep it as simple as possible and make sure that it is a fully working Rainmeter config (i.e. it includes all graphics too). If you are reporting a crash bug please include a download link to the crash dump: http://code.google.com/p/rainmeter/wiki/CrashBugs What steps will reproduce the problem? 1.just installed it 2.ran it 3.got the error What is the expected output? What do you see instead? What version of the product are you using? On what operating system? the one on the home page Please provide any additional information below. If the problem is a related to some config option attaching a example is always a good idea. Try to keep it as simple as possible and make sure that it is a fully working Rainmeter config (i.e. it includes all graphics too). If you are reporting a crash bug please include a download link to the crash dump: http://code.google.com/p/rainmeter/wiki/CrashBugs Dec 10, 2009 issue 81 (Rainmeter causing "system" process to tax cpu) commented on by tkach127 - Have had the same problem since i installed the latest version, at least i think so (1.1 rev 306). Running windows 7, the older version (0.14) did show a problem with the cpu vut kept shutting down. Currently rainmeter uses 1-4% cpu and about 35mb of memory, rather a lot. The solution in comment 12 reduced both the memory and cpu usage by about 5 times. Using the Tranquil skin with extra hdd's added. Cheers! Have had the same problem since i installed the latest version, at least i think so (1.1 rev 306). Running windows 7, the older version (0.14) did show a problem with the cpu vut kept shutting down. Currently rainmeter uses 1-4% cpu and about 35mb of memory, rather a lot. The solution in comment 12 reduced both the memory and cpu usage by about 5 times. Using the Tranquil skin with extra hdd's added. Cheers! Dec 10, 2009 issue 135 (Zune Plugin) reported by guidoferreyra89 - rainmeter needs a plugin that show what is being playing on Zune, there is for Itunes, Winamp, Songbird doesnt func. I hope you release a plugin for Zune. rainmeter needs a plugin that show what is being playing on Zune, there is for Itunes, Winamp, Songbird doesnt func. I hope you release a plugin for Zune. Dec 10, 2009 issue 134 (Rainmeter on Desktop) reported by guidoferreyra89 - Rainmeter cant stay on desktop. when i configure it to desktop taskbar and side bar are at the top of the "meters" and i want the metters over the side bar but in the desktop to. Im using the last version and enigma skin on winxp Rainmeter cant stay on desktop. when i configure it to desktop taskbar and side bar are at the top of the "meters" and i want the metters over the side bar but in the desktop to. Im using the last version and enigma skin on winxp Dec 10, 2009 issue 63 (Lack of Quad-Core support) commented on by EveryDayIsSaturdays - thanks this worked for me. thanks this worked for me. Dec 09, 2009 issue 81 (Rainmeter causing "system" process to tax cpu) commented on by darrenjcook - I'm running the Enigma Clock, notes, calendar, and Itunes with art. I've tried different skins and had similar results. I'm running the Enigma Clock, notes, calendar, and Itunes with art. I've tried different skins and had similar results. Dec 09, 2009 issue 81 (Rainmeter causing "system" process to tax cpu) commented on by evmckay - There is also the fact of network measures are taken...Different tools and dll's. What skin(s) are you using? There is also the fact of network measures are taken...Different tools and dll's. What skin(s) are you using? Dec 09, 2009 issue 81 (Rainmeter causing "system" process to tax cpu) commented on by darrenjcook - I haven't touched the refresh rates I haven't touched the refresh rates Dec 09, 2009 issue 81 (Rainmeter causing "system" process to tax cpu) commented on by darrenjcook - And yes, if I disable the NIC, I wont have internet And yes, if I disable the NIC, I wont have internet Dec 09, 2009 issue 81 (Rainmeter causing "system" process to tax cpu) commented on by darrenjcook - My laptop is always connected via wifi and I never have rainmeter CPU problems. My desktop is connected to a Version FIOS router via a Ethernet cable and the CPU is always high. However, when I disable my NIC on my desktop, rainmeter only uses 1-2% CPU (which I expect). My laptop is always connected via wifi and I never have rainmeter CPU problems. My desktop is connected to a Version FIOS router via a Ethernet cable and the CPU is always high. However, when I disable my NIC on my desktop, rainmeter only uses 1-2% CPU (which I expect). Dec 09, 2009 issue 81 (Rainmeter causing "system" process to tax cpu) commented on by evmckay - The issue I found is Network connections that are un-used but active. It wouls eem that Rainmeter is doing everything it can to fond a reading from a resource that may not be used, but thinks that it should be. The report will be filed in teh forums upon completion. This report will be a list of the Good, the bad, and the Ugly kind of thing. If I found a solution...I will document it. If not it will be there to be solved. I presume that you are using the Hardwire connection with your laptop...If I read the above statement correctly. What is the update time on the skin? I presume that if you disable the NIC....No internet??? The issue I found is Network connections that are un-used but active. It wouls eem that Rainmeter is doing everything it can to fond a reading from a resource that may not be used, but thinks that it should be. The report will be filed in teh forums upon completion. This report will be a list of the Good, the bad, and the Ugly kind of thing. If I found a solution...I will document it. If not it will be there to be solved. I presume that you are using the Hardwire connection with your laptop...If I read the above statement correctly. What is the update time on the skin? I presume that if you disable the NIC....No internet??? Dec 09, 2009 issue 81 (Rainmeter causing "system" process to tax cpu) commented on by darrenjcook - Thanks, but if you have found a temporary workaround to to resolve this issue I would really like to know. I don't want to be replacing NIC cards etc if it's completely unrelated. Where will this report be submitted? Thanks Thanks, but if you have found a temporary workaround to to resolve this issue I would really like to know. I don't want to be replacing NIC cards etc if it's completely unrelated. Where will this report be submitted? Thanks

r317 (* Changed the way to get the information of the multiple dis...) committed by spx268 - * Changed the way to get the information of the multiple display monitors. This change brings the order of monitors close to the order of "Display Properties" due to using EnumDisplayDevices and EnumDisplaySettings instead of EnumDisplayMonitors. (If EnumDisplayDevices failed, EnumDisplayMonitors is used as before.) ----- * Added the "Display Monitor" submenu in [Skins Menu]-[Position]. These menus convert the present position to the relative position from the specified monitor. (But the meter window doesn't move to the specified monitor area immediately. Only converts.) - "Use default: Primary monitor" removes the @-directive from WindowX/Y. - @0(@1, @2, ...) adds the specified monitor number to WindowX/Y. @0 means "The Virtual Screen". (http://msdn.microsoft.com/en-us/library/dd145136%28VS.85%29.aspx) - If "Auto-select based on window position" is checked, the WindowX and WindowY "@n" settings are made automatically based on the position of the meter's window. If a monitor is selected directly using "Display Monitor" in the Rainmeter / skin context menu, this menu is unchecked. This setting can be manually made in either the [Rainmeter] (all configs) or individual config sections of Rainmeter.ini. AutoSelectScreen If set to 1, the WindowX and WindowY "@n" settings are made automatically based on the position of the meter's window. If a monitor is selected directly using "Display Monitor" in the Rainmeter / skin context menu, this setting is reset to 0. ----- * Added the variables for multiple display monitors and the virtual screen. All X/Y positions are represented in the virtual screen coordinates. The following variables are for the virtual screen. #VSCREENAREAX# is the X-position of the left-side of the virtual screen. #VSCREENAREAY# is the Y-position of the top-side of the virtual screen. #VSCREENAREAWIDTH# is the width of the virtual screen. #VSCREENAREAHEIGHT# is the height of the virtual screen. The following variables are for the PRESENT monitor. Note that these variables automatically change by the WindowX and WindowY "@n" settings. If "@n" is not set, these variables return the value of the primary monitor. #WORKAREAX# is the X-position of the left-side of the work area. #WORKAREAY# is the Y-position of the top-side of the work area. #WORKAREAWIDTH# is the width of the work area. #WORKAREAHEIGHT# is the height of the work area. #SCREENAREAX# is the X-position of the left-side of the monitor screen. #SCREENAREAY# is the Y-position of the top-side of the monitor screen. #SCREENAREAWIDTH# is the width of the display resolution. #SCREENAREAHEIGHT# is the height of the display resolution. The following variables are for the PRIMARY monitor. #PWORKAREAX# is the X-position of the left-side of the work area. #PWORKAREAY# is the Y-position of the top-side of the work area. #PWORKAREAWIDTH# is the width of the work area. #PWORKAREAHEIGHT# is the height of the work area. #PSCREENAREAX# is the X-position of the left-side of the monitor screen. (maybe, always 0) #PSCREENAREAY# is the Y-position of the top-side of the monitor screen. (maybe, always 0) #PSCREENAREAWIDTH# is the width of the display resolution. #PSCREENAREAHEIGHT# is the height of the display resolution. The following variables are for the SPECIFIED monitor. (@n = @1, @2, ...) #WORKAREAX@n# is the X-position of the left-side of the work area. #WORKAREAY@n# is the Y-position of the top-side of the work area. #WORKAREAWIDTH@n# is the width of the work area. #WORKAREAHEIGHT@n# is the height of the work area. #SCREENAREAX@n# is the X-position of the left-side of the monitor screen. #SCREENAREAY@n# is the Y-position of the top-side of the monitor screen. #SCREENAREAWIDTH@n# is the width of the display resolution. #SCREENAREAHEIGHT@n# is the height of the display resolution. ----- * Other related changes: - Fixed the problem that the primary monitor isn't recognized correctly. - Fixed the problem that the information of the multiple display monitors is refreshed excessively. - For DynamicVariables, when display setting or workarea size has been changed, all variables are now updated to apply changed WORKAREA/SCREENAREA variables. - Fixed the problem that the "On Desktop" window isn't dragged correctly when the top-left corner of the virtual screen has negative coordinates. - Changed the way to stick the "On Desktop" window. ("SysListView32/FolderView" is used instead of "Progman/Program Manager".) ----- * Other changes: - When the meter window is draggable and isn't dragged, LeftMouseUpAction is now executed. - Added MouseDoubleClickAction (LeftMouseDoubleClickAction, RightMouseDoubleClickAction, MiddleMouseDoubleClickAction). If MouseDoubleClickAction is empty when mouse button is double- clicked, MouseDownAction is executed instead. - Fixed the problem that the Meter's hit-test code checks outside the area. - Changed the way to set the #CURRENTCONFIG#. (CMeterWindow::GetSkinName() is now used instead of parsing the path.)

* Changed the way to get the information of the multiple display monitors. This change brings the order of monitors close to the order of "Display Properties" due to using EnumDisplayDevices and EnumDisplaySettings instead of EnumDisplayMonitors. (If EnumDisplayDevices failed, EnumDisplayMonitors is used as before.) ----- * Added the "Display Monitor" submenu in [Skins Menu]-[Position]. These menus convert the present position to the relative position from the specified monitor. (But the meter window doesn't move to the specified monitor area immediately. Only converts.) - "Use default: Primary monitor" removes the @-directive from WindowX/Y. - @0(@1, @2, ...) adds the specified monitor number to WindowX/Y. @0 means "The Virtual Screen". (http://msdn.microsoft.com/en-us/library/dd145136%28VS.85%29.aspx) - If "Auto-select based on window position" is checked, the WindowX and WindowY "@n" settings are made automatically based on the position of the meter's window. If a monitor is selected directly using "Display Monitor" in the Rainmeter / skin context menu, this menu is unchecked. This setting can be manually made in either the [Rainmeter] (all configs) or individual config sections of Rainmeter.ini. AutoSelectScreen If set to 1, the WindowX and WindowY "@n" settings are made automatically based on the position of the meter's window. If a monitor is selected directly using "Display Monitor" in the Rainmeter / skin context menu, this setting is reset to 0. ----- * Added the variables for multiple display monitors and the virtual screen. All X/Y positions are represented in the virtual screen coordinates. The following variables are for the virtual screen. #VSCREENAREAX# is the X-position of the left-side of the virtual screen. #VSCREENAREAY# is the Y-position of the top-side of the virtual screen. #VSCREENAREAWIDTH# is the width of the virtual screen. #VSCREENAREAHEIGHT# is the height of the virtual screen. The following variables are for the PRESENT monitor. Note that these variables automatically change by the WindowX and WindowY "@n" settings. If "@n" is not set, these variables return the value of the primary monitor. #WORKAREAX# is the X-position of the left-side of the work area. #WORKAREAY# is the Y-position of the top-side of the work area. #WORKAREAWIDTH# is the width of the work area. #WORKAREAHEIGHT# is the height of the work area. #SCREENAREAX# is the X-position of the left-side of the monitor screen. #SCREENAREAY# is the Y-position of the top-side of the monitor screen. #SCREENAREAWIDTH# is the width of the display resolution. #SCREENAREAHEIGHT# is the height of the display resolution. The following variables are for the PRIMARY monitor. #PWORKAREAX# is the X-position of the left-side of the work area. #PWORKAREAY# is the Y-position of the top-side of the work area. #PWORKAREAWIDTH# is the width of the work area. #PWORKAREAHEIGHT# is the height of the work area. #PSCREENAREAX# is the X-position of the left-side of the monitor screen. (maybe, always 0) #PSCREENAREAY# is the Y-position of the top-side of the monitor screen. (maybe, always 0) #PSCREENAREAWIDTH# is the width of the display resolution. #PSCREENAREAHEIGHT# is the height of the display resolution. The following variables are for the SPECIFIED monitor. (@n = @1, @2, ...) #WORKAREAX@n# is the X-position of the left-side of the work area. #WORKAREAY@n# is the Y-position of the top-side of the work area. #WORKAREAWIDTH@n# is the width of the work area. #WORKAREAHEIGHT@n# is the height of the work area. #SCREENAREAX@n# is the X-position of the left-side of the monitor screen. #SCREENAREAY@n# is the Y-position of the top-side of the monitor screen. #SCREENAREAWIDTH@n# is the width of the display resolution. #SCREENAREAHEIGHT@n# is the height of the display resolution. ----- * Other related changes: - Fixed the problem that the primary monitor isn't recognized correctly. - Fixed the problem that the information of the multiple display monitors is refreshed excessively. - For DynamicVariables, when display setting or workarea size has been changed, all variables are now updated to apply changed WORKAREA/SCREENAREA variables. - Fixed the problem that the "On Desktop" window isn't dragged correctly when the top-left corner of the virtual screen has negative coordinates. - Changed the way to stick the "On Desktop" window. ("SysListView32/FolderView" is used instead of "Progman/Program Manager".) ----- * Other changes: - When the meter window is draggable and isn't dragged, LeftMouseUpAction is now executed. - Added MouseDoubleClickAction (LeftMouseDoubleClickAction, RightMouseDoubleClickAction, MiddleMouseDoubleClickAction). If MouseDoubleClickAction is empty when mouse button is double- clicked, MouseDownAction is executed instead. - Fixed the problem that the Meter's hit-test code checks outside the area. - Changed the way to set the #CURRENTCONFIG#. (CMeterWindow::GetSkinName() is now used instead of parsing the path.)

Last 7 days

Last 30 days