Jump to content

Grestorn

Members
  • Posts

    107
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Grestorn

  1. I've got a Logitech G910. And, yes, I'm using a large RemoteSensor page and I realized that the preference window will only shrink as far as allowing to see the whole page. Well, fortunately my WQHD monitor is big enough, but a normal Full-HD display would already have a problem with that window size...
  2. There seems to be an error with the key rows on my german QWERTZ keyboard: If I select QWERTZUIOP, actually the Y key is lit instead of the Z key. But if I select QWERTYUIOP, the correct line is used, i.e. the Z key is lit. Also, at least on my system, the minimum size of the AIDA64 preferences window is HUGE, 1582x1175 to be exact. I cannot make it any smaller than that. And, as D-E said, it's always very appreciated that you try to find new ways of making us geeks happy
  3. Did you see my panel? Looks like a good match to your system. If you're interested, send me a PM.
  4. Fiery, you're right of course... Your idea 2 is exactly what I had in mind. I missed that. About the matrix: If you look at the keys (at least on my G910), the keys create a slightly tilted, vertical line. Like 3, E, D, C are one line. Or 6, Z, H, N. you could use that to make tilted chars, couldn't you?
  5. One could also use the keyboard matrix as some kind of huge raster display to show some numbers or letters moving over it. That way, one could show some temperature (or whatever) in some color moving horizontally over the keyboard. Certainly a strange idea, but there you got it
  6. Ah, I see why "Temperature #1" doesn't show up. The temp. sensor header #1 on my MB is not connected. Temp 2 and 3 are shown correctly. So it seems to work fine ... Thanks a lot!
  7. Could you give me a link to 3431 please? On the webpage I can see only 3430.
  8. Thanks, that's great news! I don't mind fixing my panels, if I can get all readings. I'll let you know if build 3431 fixes my problem.
  9. Maybe a new optional setting "always show all sensor readings" would make all parties happy? I, too, have the same problem as Dschidi, btw, if you remember...
  10. Hi Fiery, in 5.20.3430 all Aquaero temperature sensor values seem to be shifted by one. I.e. the first temperature (Air inlet) is now "Temperature #2" instead of "Temperatur #1". There is no value for Temperature #1 at all anymore. See the attached screenshot. If this should be intentionally, then I'd have to rework my panels to use the correct temperature values, which would mean a whole lot of work. BTW, you told me once that the Aquaero temperature sensor values are overlying the values reported for the custom temperature sensor headers on my ASUS ROG Extreme V motherboard. Until now I could live with that, but recently, I really have use for these values. Is it not possible to make them visible by any way? Perhaps adding an offset to the sensor ID, so that the values are available at higher ID numbers?
  11. For your iPad you might want to check out this: http://forums.aida64.com/topic/2707-webdash-a-dedicated-ios-app-for-aida64/
  12. Nice. Is there a browser running on the Shield or how are you using it?
  13. Sorry for not being precise enough It's Win8.1 64bit 6.3 (Upd 1) Build 9600.17668.amd64fre.winblue_r8.150127-1500 All official updates and patches are installed About the panel: Ah I see. Interesting, though, how the LCD panels work differently: While all sensors gauges, bars and displays seem to update like once a second, the graphs are actually updated much more often, like once every 350 ms, even faster than the 500ms I've set in the prefs.
  14. Windows 8.1 Thanks for looking into it. BTW, is the limit of the update frequency of the Sensor Panel set to 1000 ms intentionally? All other panels can update every 500ms, but not the Sensor Panel I understand that you don't want to cause system instabilities and performance problems by allowing to fast updates. Still, it would be great to have an option to allow faster updates for the panels, on our own risk of course.
  15. I just found a problem with the latest AIDA version: After standby certain sensors cease to update. Especially the Thermaltake DPS-G values are all stuck to the same value indefinitely. Stopping AIDA and starting it again resolves the problem.
  16. Ok. As we Germans say: sehr schade! (a real pity) Thanks for the answer though.
  17. Strange, as it's supposed to do that (but I never tried it myself, to be honest). Still it would make the window bottom-most which would have it's own advantages (never obscuring any other window) and behaving like being part of the desktop itself. Sorry, I missed that explanation (and I can't find it in this thread either ). I don't want to intrude, especially since I don't know how you implemented the SensorPanel, but I'd like to point out that it is possible to define a transparent color key for standard windows: https://msdn.microsoft.com/en-us/library/ms997507.aspx?f=255&MSPPError=-2147217396 It would not be possible to make the background be transparent just like that, but the user could select a color of his choice to be transparent, and where ever this color is used in the SensorPanel (on the background for example) the window would become transparent. If this doesn't work for you for some reason, then please don't be offended by me making that suggestion...
  18. A nice feature would be the possibility to set the SensorPanel as the BottomMost window on the desktop. I.e. the panel would act like a part of the desktop background itself, it wouldn't interfere with any Window on the desktop, would never obstruct any other window and wouldn't minimize when using Windows-D either. This can be achieved using the user32.dll. You have to use FindWindow("ProgMan") and use the returned handle as the parent of your own Window (in this case the SensorPanel). Here's an example for WPF/C#, but you can certainly adapt that to every other programming environment: http://www.tsql.de/tag/setparent And while I'm at it: Another great option would be to set the SensorPanel's background as transparent. That way you could place the elements freely on the desktop as you need them without obstructing the wallpaper.
  19. A simple solution would be a configurable hot key which shows/hides the panel, wouldn't it? If you're providing a small tool for this functionality (like "ShowPanel.exe", which could be started with an option like /show and /hide) which could be started through a Windows shortcut, this could be done with Windows' own facilities, by defining a hot key for that shortcut.
  20. I've just had the same error myself (and have seen it in the past as well) Starting the update again (using Check For Update) usually works fine, sometimes you have to start it twice. AIDA is running using elevated privileges of course.
  21. Well, I thought so, too, but Fiery explained that since the rendering on Arx and and RemoteSensor is done using HTML, there are certain restrictions and deviations from the preview and the end result.
×
×
  • Create New...