Open GoogleCodeExporter opened 9 years ago
Original comment by moel.mich
on 5 Apr 2010 at 3:35
I might have a play with this. Moel, is there any logical place for this in the
code or should I split it out into a new project?
Original comment by volta...@voltagex.org
on 22 Nov 2010 at 8:33
I think the best place to add it would be in the GUI project
"OpenHardwareMonitor" (not the "OpenHardwareMonitorLib") by creating a few
classes which separate it as good as possible from the GUI. If you create more
than one class it might be a good idea to move everything into a new
subnamespace. Good samples how to integrate code to present data on additional
interfaces is the WMI provider implementation
http://code.google.com/p/open-hardware-monitor/source/browse/trunk/WMI/ or the
gadget
http://code.google.com/p/open-hardware-monitor/source/browse/trunk/GUI/SensorGad
get.cs
Theoretically you could also create a new project and just use the
OpenHardwareMonitorLib (like the OpenHardwareMonitor project does). But this
has some disadvantages, as some hardware can only be accessed by one process at
a time. So for this hardware you could only use the Open Hardware Monitor GUI
or the new project, but not both at the same time.
Original comment by moel.mich
on 22 Nov 2010 at 9:28
I had a bit of a look at this yesterday, I can't find the C# G15 wrapper I was
using right now but we'll need to talk to the author about its licence, and the
easiest way for me to integrate it would be to bind to something like an
"OnSensorUpdate" event - then you call G15.DrawLoop()
I'll post more details later, but the problem I had was getting the G15 DLLs to
build in the correct order.
Original comment by volta...@voltagex.org
on 23 Nov 2010 at 3:40
Library is at: http://envy.mrjul.com/
Moel, if you have some time, can you have a look at the way this library
builds? I was having to manually include its Native.dll in OpenHardwareLib to
avoid errors - when I'd rather just use a project reference.
Original comment by volta...@voltagex.org
on 23 Nov 2010 at 4:23
I is there any progress on this. I would be very interested in looking at the
source for this
Original comment by Northlo...@gmail.com
on 24 Nov 2011 at 7:53
Has there been any progress on this one?
If not, I could properly contribute with the needed stuff. I've already written
a G15 lcd driver for .NET for another project.
Original comment by mar...@martinnyhjem.dk
on 13 Jul 2012 at 7:17
[deleted comment]
I'm working on it.
I have a project running for this.
All infromation can be found at:
https://bitbucket.org/jimmyD/open-hardware-monitor-applet/wiki/Home
At this moment there is G15 support. G19 support will be added later.
Original comment by dom.ji...@gmail.com
on 3 Aug 2012 at 2:00
[deleted comment]
This is a better link.
https://bitbucket.org/jimmyD/open-hardware-monitor-applet/downloads
Original comment by dom.ji...@gmail.com
on 5 Aug 2012 at 6:48
The Hardware Monitor applet has been moved to another location.
You can find it on:
https://bitbucket.org/jimmyD/hardware-monitor-applet/wiki/Home
Original comment by dom.ji...@gmail.com
on 25 Apr 2015 at 7:15
Original issue reported on code.google.com by
invisib...@invisibill.net
on 5 Apr 2010 at 5:06