nvDock
This was a little application I made really because I was bored. At the time I was tweaking my Linux machine to run games as well as I could, and often you had to edit video driver settings for each game to make it run right. So I made this little icon dock so I could easy launch the settings and monitor my GPU temperature. I had no idea it was going to become so popular as to even make it into the distributions of other distros.
Hover over it and it will tell you your GPU temperature if your card is into that kind of thing. A double click will launch the NVIDIA settings control panel, and right click will bring up a nifty menu with a few options. Also on the menu it will show the NVIDIA driver version, which is surely to come in handy at least one time in your life.
NVDock is written in C, and uses the GtkStatusIcon functionality which if my memory serves me correct, requires GTK 2.10 or newer. Obviously it also requires that your window manager has a system tray… most do anymore.
Download
- nvDock 1.02 Source
- nvDock 1.02 Binary (Linux i686, glibc 2.5)
SVN Access
Development Branch
- svn checkout http://bobmajdakjr.googlecode.com/svn/trunk/nvdock nvdock
Checkout Version 1.02
- svn checkout http://bobmajdakjr.googlecode.com/svn/tags/nvdock-1.02 nvdock
Comments
Write a Comment
- Words
- See Also
- Locator
- Things
- World of Warcraft
- Blogroll
- Twit
- Sites
-
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||
I'm trying to use nvdock on opensuse11.4 but it crashes when right clicking the icon. I believe it has to with the fact that I use a virtual desktop with a large size :
Option "metamodes" "1920x1080 @3840x2160
The following output is dumped in my console when it crashes :
(:6876): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width 174 and height -832
The program '' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 504 error_code 11 request_code 53 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Can you do anything?
Thx,
Guy.