yujitach / menumeters Goto Github PK
View Code? Open in Web Editor NEWmy fork of MenuMeters by http://www.ragingmenace.com/software/menumeters/
License: GNU General Public License v2.0
my fork of MenuMeters by http://www.ragingmenace.com/software/menumeters/
License: GNU General Public License v2.0
Just for info, your version of menu meters is working on my OSX Sierra Hackintosh. However one minor glitch, my quad core cpu is showing as an 8 core cpu.
I didn't do any real testing, but I did want to mention that it does load and seems to work well in a minute's checking under OS X 10.10.5
Would it be easy to add process information to the menus?
I've got the following message by email:
On a 12-core Mac Pro, if I turn off “show average for multiple processors as a single display”, the only display option that will display anything is thermometer. I would like to display graph, but if any of the other options are chosen, nothing is displayed.
The resulting prefPane cannot be installed on OS X 10.11.1
Double-clicking the prefPane will result in error:
"'MenuMeters.prefPane' is damaged and can't be opened. You should move it to the Trash."
I have re-downloaded the zip archive and retried, to no avail.
Please verify compatibility with OS X 10.11.1 and advise.
When I try and open the preference pane in Sierra I get the following error:
"Preferences Error
Could not load MenuMeters preference pane."
Are there any plans for an update that introduces support for macOS Sierra?
Perhaps this is to be expected, but I didn't notice a warning: I tried to install this version on Yosemite, but the SysPref fails to open. The following is logged to Console.app:
Oct 5 13:47:06 xxx.rrz.uni-koeln.de System Preferences[81876]: Failed to connect (memPagerateColor) outlet from (MenuMetersPref) to (NSColorWell): missing setter or instance variable
Oct 5 13:47:06 xxx.rrz.uni-koeln.de System Preferences[81876]: Failed to connect (memPagerateColorLabel) outlet from (MenuMetersPref) to (NSTextField): missing setter or instance variable
Oct 5 13:47:06 xxx.rrz.uni-koeln.de System Preferences[81876]: ### com.ragingmenace.MenuMeters instantiatePrefPaneObject exception:*** -[NSURL initFileURLWithPath:]: nil string parameter
Hi,, i want to ask you that when Your code i am using for iPhone 6 Free memory state then sometime its showing Free memory greater then The Total memory like: My Total ram is - 989 and And Free ram is 1.29 GB and Some time its Showing Correct data and its working Fine, please tell whats going wrong there then i can identify what i am doing wrong
I'm using a mid-2012 Macbook Pro running El Capitan 10.11.1. I can open the downloaded zip file, but the resulting preference pane will not load. Thanks for tips.
I'm using the Memory Menu Meter and have the update interval set to 10 seconds. However it doesn't seem to be respected. The menu seems to get updated every second.
Long time Snow Leopard user of Menu Meters who just bought a new MacBook. Thanks for updating this for El Capitan. I've just installed it and it works fine - I did try the original installer a few days ago and yes, completely incompatible. I easily removed it using the installer (but I could have removed it manually instead in Library>PreferencePanes). I cannot find how to remove your version nor can I find its location.
I have an enhancement request, is it possible to remove the CPU hit for monitoring options not needed? I know this is minor, but over sometimes several days without access to power, the battery life hit can be significant. Perhaps with the same checkbox used to toggle display. I played with extending the update intervals on unused items to no effect. Playing with intervals revealed a CPU use with a minimum of around 2% as measured by the activity monitor that I could not drop further.
Thanks!
Hi there!
I definitely noticed files copy slowdown when "Display Disc Activity Menu Meter" is "on". Was under copy of 8GB file from my internal SSD to external USB Flash Drive. When I disabled "Disc Activity", copy speed returned back to normal (was near 100 times slower). When enabled -- slowed down again. My settings attached (update interval: 2 sec.). Maybe happens only with USB Flash Drives.
If you have time, you can check this.
Having several network connections like ethernet, Wifi, etc. my primary interface if the wrong one. Selecting from the menu "Display this interface" seems to do nothing for the network menu item.
When a user switches to Dark Mode, textual elements render properly (switching from dark to light colors).
When a user switches from DarkMode, textual elements remain light colors, rendering them invisible.
I've attached a gif of the issue (note - the gif loops, so it makes it look like the text eventually renders - but it does not).
Would you mind posting the releases here (in the release section of your GitHub repo)? It will give your release more legitimacy if the binaries are served here rather than on your personal website. Your release is for now the de facto standard and the main release, so it merits a legit hosting, and inclusion in package managers such as homebrew cask.
Thank's for your work.
But when I install app from http://member.ipmu.jp/yuji.tachikawa/MenuMetersElCapitan/zips/MenuMeters_1.9.zip
I get error "Could not load MenuMeters preference pane."
I noticed that the CPU temperature is part of the CPU usage bar graph, but I thought it would be nice to include it in the CPU dropdown menu where it shows Threads/Load Average, etc.
Hi, I'm just curious if there was a particular reason for not being able to set the colors for disk related visuals. Every other type of visual allows setting of color so it just seems a bit odd so I'm guessing there is a reason but I couldn't find any other issues relating to this. Not requesting a feature here. This is just an enquiry.
I just tried a different app for displaying cpu and memory information in the menubar and it had an option to show the current memory pressure (as in Activity Monitor) instead of the actual used/free memory. I really liked that, would it be possible to implement this in MenuMeters?
The prefPane inside the 1.9.4 download zip reports it is version 1.9.3
http://member.ipmu.jp/yuji.tachikawa/MenuMetersElCapitan/zips/MenuMeters_1.9.4.zip
Having updated to the latest OS X on my MacBook Pro 13" (Early 2011), the menu meters still show as they were configured before the update, but I can no longer access the preference pane to make any changes. Clicking on the icon does not do anything. Reinstalling the preference pane does not do anything either.
I am able to drag and re-order other system icons in menu bar like date, power status, wifi, volume etc. but not the menumeter icons.
When you select usage history graph, the memory pressure box gets grayed out. Would be nice to have that work.
I'd be very interested in having a menu meter that displays the load average(s) for the system. Would that be a difficult feature to add to MenuMeters?
On latest public beta of El Capitan. The display CPU checkbox doesn't toggle on/off correctly, nor does the option to show average for multiple processors as single display work at all any more. Sometimes I really need that latter option to allow a number of menu items to display properly (even with consolidation with the Bartender app). I tried the Restart SystemUIServer script to see if it would influence the MenuMeter settings changes; it didn't.
@geigi Thank you for the contribution of the memory pressure stats. I should have tested it earlier when it was still an open PR but since Yuji made the new binary public today I gave it a go. On my system (Mac Mini with 16GB RAM, Sierra 10.12.3) the pressure bar in MenuMeters doesn't seem to align with the values in Activity Monitor.
For example, see the screenshot below, where Activity Monitor shows pressure at around 45% but the Menubar appears to be around 25%
I then proceeded to launch as many apps as possible to try to increase the pressure, and while Activity Monitor's graph steadily increased, the MenuMeter seemed to stay stagnant. I had my update value at 10seconds (default)
Any idea why that might be?
For more reliable and persistent hosting you might want to consider hosting the binaries using Github's "Releases" feature. This is a very common practice for packages distributed via homebrew-cask:
Here's a set of examples from the files found in https://github.com/caskroom/homebrew-cask/tree/master/Casks
> grep url * | grep github | head
aether.rb: url "https://github.com/nehbit/aether-public/releases/download/v#{version}-OSX/Aether.#{version}.dmg"
aluxian-messenger.rb: url "https://github.com/Aluxian/Facebook-Messenger-Desktop/releases/download/v#{version}/Messenger.dmg"
androidtool.rb: url "https://github.com/mortenjust/androidtool-mac/releases/download/#{version}/AndroidTool.zip"
angry-ip-scanner.rb: url "https://github.com/angryziber/ipscan/releases/download/#{version}/ipscan-mac-#{version}.zip"
anybar.rb: url "https://github.com/tonsky/AnyBar/releases/download/#{version}/AnyBar-#{version}.zip"
apns-pusher.rb: url "https://github.com/KnuffApp/APNS-Pusher/releases/download/v#{version}/APNS.Pusher.app.zip"
appserver.rb: url "https://github.com/appserver-io/appserver/releases/download/#{version.sub(/-.*/, '')}/appserver-dist_#{version}_x86_64.pkg"
aptanastudio.rb: url "https://github.com/aptana/studio3/releases/download/v#{version}/Aptana_Studio_3_Setup_#{version}.dmg"
aquamacs.rb: url "https://github.com/davidswelt/aquamacs-emacs/releases/download/Aquamacs-#{version}-final/Aquamacs-Emacs-#{version}final.tar.bz2"
aquamacs.rb: url "https://github.com/davidswelt/aquamacs-emacs/releases/download/Aquamacs-#{version}/Aquamacs-Emacs-#{version}.dmg"
I created an example release in a fork of this repo using the 1.9.1
tag and uploaded the zip file found here which results in the same file available here:
https://github.com/jalessio/MenuMeters/releases/download/1.9.1/MenuMeters_1.9.1.zip
Here's the "releases" page:
https://github.com/jalessio/MenuMeters/releases
And here's a proposed corresponding change to homebrew-cask to adjust to the new URL (just remove the jalessio
part to switch it over to your repo):
jalessio/homebrew-cask@60b8e52
This is not essential, but removes the need to host the file yourself (see #7) and provides a long-lived location for all versions of the files. Thanks!
Hello!
If you willing to take two features from my repo, feel free. Screenshots available. Or put a link on the main project page for people who may care about it.
MenuMeters 1.9.1 seems to interfere with OS X Server 5 based Time Machine Service causing
note: local time machine backups (e.g. on an external usb-HD) are not affected.
Is the server down?
When MenuMeters is left running over several days, I notice that WindowServer starts taking up more and more CPU load, to the extent where my Mac becomes extremely slow.
Going into the preference pane and toggling each display immediately releases whatever resources are tied up, with visible results in Activity Monitor.
This is happening in OS X Sierra 10.12.1. It might not be immediately noticeable in modern machines, but on a six-year-old Mac mini it effectively cripples the machine in two days of uptime.
I just installed El Capitan and your build of menu meters. I choose to instal the pref pane for all users. When I try to click to engage a menu I get the error: "Menu Extra Could Not Load."
I deleted and installed for single user only. I can check the box to turn on a menu, but nothing happens when I come back the box is unchecked again.
UPDATE
Tried a third (single user only). It seems to work.
I was playing with dtrace on my system and saw regular mmap
calls from MenuMeters and went looking into it.
It seems that the NSImage used to draw an update is always created new.
see: https://github.com/yujitach/MenuMeters/blob/master/MenuExtras/MenuMeterCPU/MenuMeterCPUExtra.m#L221
// Image to render into (and return to view)
NSImage *currentImage = [[NSImage alloc] initWithSize:NSMakeSize((float)menuWidth,
though I'm not a objC programmer.
I think we could invest the extra effort to reduce the resource usage to lower the resource impact of MenuMeters even more by using some sort of double buffering, or reusing the previous NSImage instance.
dtrace -n 'syscall::mmap:entry /pid==283/ { @[ustack()] = count(); } syscall::munmap:entry /pid==283/ {@[ustack()] = count();}'
dtrace: description 'syscall::mmap:entry ' matched 2 probes
^C
libsystem_kernel.dylib`__mmap+0xa
CoreGraphics`CGBitmapAllocateData+0x52
AppKit`NSNewBitmapBackingStore+0xac
AppKit`+[NSCGImageSnapshotRep _lockFocusForCreatingSnapshot:withRect:context:hints:flipped:]+0x356
AppKit`+[NSCGImageSnapshotRep lockFocusForCreatingSnapshotWithRect:context:hints:flipped:]+0x46
AppKit`-[NSImage _lockFocusOnRepresentation:rect:context:hints:flipped:]+0x377
AppKit`__51-[NSImage lockFocusWithRect:context:hints:flipped:]_block_invoke+0x52
AppKit`-[NSImage _usingBestRepresentationForRect:context:hints:body:]+0xa4
AppKit`-[NSImage lockFocusWithRect:context:hints:flipped:]+0x9e
AppKit`-[NSImage lockFocusFlipped:]+0x7b
MenuMetersApp`-[MenuMeterMemExtra renderNumbersIntoImage:]+0x11c
MenuMetersApp`-[MenuMeterMemExtra image]+0x134
MenuMetersApp`-[MenuMetersMenuExtraBase timerFired:]+0x156
MenuMetersApp`-[MenuMeterMemExtra timerFired:]+0x16e
Foundation`__NSFireTimer+0x53
CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+0x14
CoreFoundation`__CFRunLoopDoTimer+0x42f
CoreFoundation`__CFRunLoopDoTimers+0x12a
CoreFoundation`__CFRunLoopRun+0x7d7
CoreFoundation`CFRunLoopRunSpecific+0x1a4
3
libsystem_kernel.dylib`__mmap+0xa
CoreGraphics`CGBitmapAllocateData+0x52
AppKit`NSNewBitmapBackingStore+0xac
AppKit`+[NSCGImageSnapshotRep _lockFocusForCreatingSnapshot:withRect:context:hints:flipped:]+0x356
AppKit`+[NSCGImageSnapshotRep lockFocusForCreatingSnapshotWithRect:context:hints:flipped:]+0x46
AppKit`-[NSImage _lockFocusOnRepresentation:rect:context:hints:flipped:]+0x377
AppKit`__51-[NSImage lockFocusWithRect:context:hints:flipped:]_block_invoke+0x52
AppKit`-[NSImage _usingBestRepresentationForRect:context:hints:body:]+0xa4
AppKit`-[NSImage lockFocusWithRect:context:hints:flipped:]+0x9e
AppKit`-[NSImage lockFocusFlipped:]+0x7b
MenuMetersApp`-[MenuMetersMenuExtraBase timerFired:]+0x174
MenuMetersApp`-[MenuMeterMemExtra timerFired:]+0x16e
Foundation`__NSFireTimer+0x53
CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+0x14
CoreFoundation`__CFRunLoopDoTimer+0x42f
CoreFoundation`__CFRunLoopDoTimers+0x12a
CoreFoundation`__CFRunLoopRun+0x7d7
CoreFoundation`CFRunLoopRunSpecific+0x1a4
HIToolbox`RunCurrentEventLoopInMode+0xf0
HIToolbox`ReceiveNextEventCommon+0x1b0
3
libsystem_kernel.dylib`__mmap+0xa
CoreGraphics`CGBitmapAllocateData+0x52
AppKit`NSNewBitmapBackingStore+0xac
AppKit`+[NSCGImageSnapshotRep _lockFocusForCreatingSnapshot:withRect:context:hints:flipped:]+0x356
AppKit`+[NSCGImageSnapshotRep lockFocusForCreatingSnapshotWithRect:context:hints:flipped:]+0x46
AppKit`-[NSImage _lockFocusOnRepresentation:rect:context:hints:flipped:]+0x377
AppKit`__51-[NSImage lockFocusWithRect:context:hints:flipped:]_block_invoke+0x52
AppKit`-[NSImage _usingBestRepresentationForRect:context:hints:body:]+0xa4
AppKit`-[NSImage lockFocusWithRect:context:hints:flipped:]+0x9e
AppKit`-[NSImage lockFocusFlipped:]+0x7b
MenuMetersApp`-[MenuMeterCPUExtra renderHistoryGraphIntoImage:forProcessor:atOffset:]+0x52f
MenuMetersApp`-[MenuMeterCPUExtra image]+0x1da
MenuMetersApp`-[MenuMetersMenuExtraBase timerFired:]+0x156
MenuMetersApp`-[MenuMeterCPUExtra timerFired:]+0x1a4
Foundation`__NSFireTimer+0x53
CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+0x14
CoreFoundation`__CFRunLoopDoTimer+0x42f
CoreFoundation`__CFRunLoopDoTimers+0x12a
CoreFoundation`__CFRunLoopRun+0x7d7
CoreFoundation`CFRunLoopRunSpecific+0x1a4
9
libsystem_kernel.dylib`__mmap+0xa
CoreGraphics`CGBitmapAllocateData+0x52
AppKit`NSNewBitmapBackingStore+0xac
AppKit`+[NSCGImageSnapshotRep _lockFocusForCreatingSnapshot:withRect:context:hints:flipped:]+0x356
AppKit`+[NSCGImageSnapshotRep lockFocusForCreatingSnapshotWithRect:context:hints:flipped:]+0x46
AppKit`-[NSImage _lockFocusOnRepresentation:rect:context:hints:flipped:]+0x377
AppKit`__51-[NSImage lockFocusWithRect:context:hints:flipped:]_block_invoke+0x52
AppKit`-[NSImage _usingBestRepresentationForRect:context:hints:body:]+0xa4
AppKit`-[NSImage lockFocusWithRect:context:hints:flipped:]+0x9e
AppKit`-[NSImage lockFocusFlipped:]+0x7b
MenuMetersApp`-[MenuMeterNetExtra renderThroughputIntoImage:]+0x3a2
MenuMetersApp`-[MenuMeterNetExtra image]+0x125
MenuMetersApp`-[MenuMetersMenuExtraBase timerFired:]+0x156
MenuMetersApp`-[MenuMeterNetExtra timerFired:]+0x2c4
Foundation`__NSFireTimer+0x53
CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+0x14
CoreFoundation`__CFRunLoopDoTimer+0x42f
CoreFoundation`__CFRunLoopDoTimers+0x12a
CoreFoundation`__CFRunLoopRun+0x7d7
CoreFoundation`CFRunLoopRunSpecific+0x1a4
9
libsystem_kernel.dylib`__mmap+0xa
CoreGraphics`CGBitmapAllocateData+0x52
AppKit`NSNewBitmapBackingStore+0xac
AppKit`+[NSCGImageSnapshotRep _lockFocusForCreatingSnapshot:withRect:context:hints:flipped:]+0x356
AppKit`+[NSCGImageSnapshotRep lockFocusForCreatingSnapshotWithRect:context:hints:flipped:]+0x46
AppKit`-[NSImage _lockFocusOnRepresentation:rect:context:hints:flipped:]+0x377
AppKit`__51-[NSImage lockFocusWithRect:context:hints:flipped:]_block_invoke+0x52
AppKit`-[NSImage _usingBestRepresentationForRect:context:hints:body:]+0xa4
AppKit`-[NSImage lockFocusWithRect:context:hints:flipped:]+0x9e
AppKit`-[NSImage lockFocusFlipped:]+0x7b
MenuMetersApp`-[MenuMetersMenuExtraBase timerFired:]+0x174
MenuMetersApp`-[MenuMeterNetExtra timerFired:]+0x2c4
Foundation`__NSFireTimer+0x53
CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+0x14
CoreFoundation`__CFRunLoopDoTimer+0x42f
CoreFoundation`__CFRunLoopDoTimers+0x12a
CoreFoundation`__CFRunLoopRun+0x7d7
CoreFoundation`CFRunLoopRunSpecific+0x1a4
HIToolbox`RunCurrentEventLoopInMode+0xf0
HIToolbox`ReceiveNextEventCommon+0x1b0
9
libsystem_kernel.dylib`__mmap+0xa
CoreGraphics`CGBitmapAllocateData+0x52
AppKit`NSNewBitmapBackingStore+0xac
AppKit`+[NSCGImageSnapshotRep _lockFocusForCreatingSnapshot:withRect:context:hints:flipped:]+0x356
AppKit`+[NSCGImageSnapshotRep lockFocusForCreatingSnapshotWithRect:context:hints:flipped:]+0x46
AppKit`-[NSImage _lockFocusOnRepresentation:rect:context:hints:flipped:]+0x377
AppKit`__51-[NSImage lockFocusWithRect:context:hints:flipped:]_block_invoke+0x52
AppKit`-[NSImage _usingBestRepresentationForRect:context:hints:body:]+0xa4
AppKit`-[NSImage lockFocusWithRect:context:hints:flipped:]+0x9e
AppKit`-[NSImage lockFocusFlipped:]+0x7b
MenuMetersApp`-[MenuMetersMenuExtraBase timerFired:]+0x174
MenuMetersApp`-[MenuMeterCPUExtra timerFired:]+0x1a4
Foundation`__NSFireTimer+0x53
CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+0x14
CoreFoundation`__CFRunLoopDoTimer+0x42f
CoreFoundation`__CFRunLoopDoTimers+0x12a
CoreFoundation`__CFRunLoopRun+0x7d7
CoreFoundation`CFRunLoopRunSpecific+0x1a4
HIToolbox`RunCurrentEventLoopInMode+0xf0
HIToolbox`ReceiveNextEventCommon+0x1b0
9
libsystem_kernel.dylib`__munmap+0xa
AppKit`-[NSCustomReleaseData dealloc]+0x2c
CoreGraphics`data_provider_finalize+0x67
CoreFoundation`_CFRelease+0x123
CoreGraphics`image_finalize+0x53
CoreFoundation`_CFRelease+0x123
libobjc.A.dylib`(anonymous namespace)::AutoreleasePoolPage::pop(void*)+0x30d
CoreFoundation`_CFAutoreleasePoolPop+0x16
CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+0x14
CoreFoundation`__CFRunLoopDoTimer+0x42f
CoreFoundation`__CFRunLoopDoTimers+0x12a
CoreFoundation`__CFRunLoopRun+0x7d7
CoreFoundation`CFRunLoopRunSpecific+0x1a4
HIToolbox`RunCurrentEventLoopInMode+0xf0
HIToolbox`ReceiveNextEventCommon+0x1b0
HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter+0x47
AppKit`_DPSNextEvent+0x460
AppKit`-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+0xae5
AppKit`-[NSApplication run]+0x39e
AppKit`NSApplicationMain+0x4d5
21
libsystem_kernel.dylib`__munmap+0xa
AppKit`-[NSCustomReleaseData dealloc]+0x2c
AppKit`-[NSSnapshotBitmapGraphicsContext dealloc]+0x40
libobjc.A.dylib`(anonymous namespace)::AutoreleasePoolPage::pop(void*)+0x30d
CoreFoundation`_CFAutoreleasePoolPop+0x16
CoreFoundation`__CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__+0x14
CoreFoundation`__CFRunLoopDoTimer+0x42f
CoreFoundation`__CFRunLoopDoTimers+0x12a
CoreFoundation`__CFRunLoopRun+0x7d7
CoreFoundation`CFRunLoopRunSpecific+0x1a4
HIToolbox`RunCurrentEventLoopInMode+0xf0
HIToolbox`ReceiveNextEventCommon+0x1b0
HIToolbox`_BlockUntilNextEventMatchingListInModeWithFilter+0x47
AppKit`_DPSNextEvent+0x460
AppKit`-[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:]+0xae5
AppKit`-[NSApplication run]+0x39e
AppKit`NSApplicationMain+0x4d5
libdyld.dylib`start+0x1
MenuMetersApp`0x2
21
It would be nice to have ability reset traffic usage values w/o restart mac.
Download the precompiled binaries and install by double-clicking on MenuMeters.prefPane
. This will trigger App Translocation, which isolates MenuMeters.app
to a read only filesystem with a random mount point:
$ df -h
Filesystem Size Used Avail Capacity iused ifree %iused Mounted on
/Users/cambecc/Library/PreferencePanes/MenuMeters.prefPane/Contents/Resources/MenuMetersApp.app 931Gi 40Gi 890Gi 5% 1330281 4293636998 0% /private/var/folders/2z/9vfqf31x1l2bk7n92vrqz4500000gn/T/AppTranslocation/248A0569-0947-496E-9BD9-B66D59B5273E
The app seems to work but it's not ideal to have these weird file systems sitting around forever. One workaround is to strip the quarantine extended attribute from the .zip file before installation:
xattr -d com.apple.quarantine MenuMeters_1.9.3.zip
Is there a better way to resolve this for people using the precompiled binaries?
Most likely, building from source would not run into this issue.
Thanks for porting this!
I'm connected with my WiFi and the networkmeter works great!
But if I'm connected to a VPN, the VPN-connection is always 0 up/down, so I switch to the WiFi-connection and select "show this interface" via the menu - which is not working. VPN-connection is still selected and I can't change the interface for measuring.
Is there any solution?
Thank you very much for your fork btw!
Sorry to bother you but, as I was very happy to see your posting, I immediately tried to build your version of MenuMeters...
It was sad to find out that nothing showed up in my ~/Library/PreferencePanes... Build succeeded, no errors!
I tried to compile it on Yosemite 10.10.5 as wll as El Capitan 10.11 beta 8... Same results...
What could have gone wrong here?
Kind regards,
Adam
It does not work. The Preference Pane is shown as usual but there is nothing in Menu Bar. I've been looking for a explanation for this behavior and I've found that the App in "... Contents/Resources/MenuMeters App" has a forbidden in her icon. I've uploaded an image to illustrate this. It seems the App is not compatible. What a weird!
Hello,
The preference pane is there in system preferences. When clicking on let's say "Display Network Menu Meter" - about 10 seconds later a popup happens:
"Menu Extra Could Not Load"
For instructions on enabling third-party menu extras please see the documentation.
console.log says default
21:02:22.917911 -0400 SystemUIServer invalid menu extra: /Library/PreferencePanes/MenuMeters.prefPane/Contents/Resources/MenuCracker.menu
default 21:02:22.918020 -0400 SystemUIServer unable to load menu extra: /Library/PreferencePanes/MenuMeters.prefPane/Contents/Resources/MenuCracker.menu
As explained elsewhere, as of Sierra 10.12, macOS supports command-dragging 3rd party menu items (NSStatusItems), including this lovely fork.
Considering the existence of MenuCracker was for precisely this purpose, it's nice to see support officially finally land after all these years.
@yujitach Happy to send a PR to update the read me if you'd like -- please just point me in the right direction.
http://member.ipmu.jp/yuji.tachikawa/MenuMetersElCapitan/ says:
One good thing about the former is that you can rearrange them by ⌘-dragging the menu items. I have no idea why ⌘-dragging is not provided for the latter by the system.
Just tried this on 10.12.4. ⌘-dragging reorders NSMenuExtras and NSStatusItems as desired, and the ordering persists across logout.
I've edited my preferences to only show the Disk and CPU usage charts, and to show multiple processors as multiple charts. Each time that I restart my computer, these settings revert to default.
Running OS X 10.11.6 and MenuMeters port 1.9.2
I have now 4 times each menubar display for each item I enable.
How do I get back to one?
Might be upgrade leftovers but dont know where to fix this.
Hi there,
Thanks for your work on this. I found an issue with Public Beta 4 that didn't occur earlier. Removing a prefpane works fine, but adding it back in creates the following exception:
Exception Name: NSInvalidArgumentException
Description: *** -[NSURL initFileURLWithPath:]: nil string parameter
User Info: (null)
0 CoreFoundation 0x000000010b03e7dc __exceptionPreprocess + 172
1 libobjc.A.dylib 0x00000001095c9810 objc_exception_throw + 48
2 CoreFoundation 0x000000010b03e68d +[NSException raise:format:] + 205
3 Foundation 0x000000010901ea15 -[NSURL(NSURL) initFileURLWithPath:] + 131
4 Foundation 0x000000010901e97d +[NSURL(NSURL) fileURLWithPath:] + 45
5 MenuMeters 0x000000011c08282c -[MenuMetersPref netPrefChange:] + 235
6 libsystem_trace.dylib 0x000000010d633082 _os_activity_initiate + 75
7 AppKit 0x0000000109c4ad8d -[NSApplication sendAction:to:from:] + 460
8 AppKit 0x0000000109c5fcea -[NSControl sendAction:to:] + 86
9 AppKit 0x0000000109c5fc14 __26-[NSCell _sendActionFrom:]_block_invoke + 131
10 libsystem_trace.dylib 0x000000010d633082 _os_activity_initiate + 75
11 AppKit 0x0000000109c5fb71 -[NSCell _sendActionFrom:] + 144
12 libsystem_trace.dylib 0x000000010d633082 _os_activity_initiate + 75
13 AppKit 0x0000000109c5e196 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 2693
14 AppKit 0x0000000109cb3512 -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 744
15 AppKit 0x0000000109c5c8ce -[NSControl mouseDown:] + 657
16 AppKit 0x000000010a20212b -[NSWindow _handleMouseDownEvent:isDelayedEvent:] + 6273
17 AppKit 0x000000010a20341c -[NSWindow _reallySendEvent:isDelayedEvent:] + 212
18 AppKit 0x0000000109b63c60 -[NSWindow sendEvent:] + 532
19 System Preferences 0x000000010836a816 System Preferences + 30742
20 AppKit 0x0000000109b6037c -[NSApplication sendEvent:] + 2540
21 System Preferences 0x0000000108369ec4 System Preferences + 28356
22 AppKit 0x0000000109a939f8 -[NSApplication run] + 796
23 AppKit 0x0000000109a15e9a NSApplicationMain + 1176
24 libdyld.dylib 0x000000010d2c05ad start + 1
Thanks for all your efforts here! We're really happy that MM is not dead!
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.