Jump to content

BHSY

Members
 View Profile  See their activity

  • Posts

    198

  • Joined

  • Last visited

  • Days Won

    30

 Content Type 

Everything posted by BHSY

  1. BHSY
    I see. Thank you so much.
  2. BHSY
    Yes, it's a good practice for us. However, for point number 2, the graph and gauge label was not updated automatically when we use the 'Change Source'.
  3. BHSY
    Correct me if I'm wrong but I think the label you mention to Surjeet refers to the 'Simple sensor item', am I right? What about the gauge/custom gauge? Can the gauge/custom gauge description be changed automatically on the SensorPanel Manager? For example, after I duplicate the CPU temperature gauge and change it to GPU temperature gauge using the 'Change Source', only the icon has changed but the description still shows as CPU Utilization (Please take a look at the attached image). The only way to change it is to go back to the Modify window but that defeats the purpose of using the 'Change Source'.
  4. BHSY
    Thank you. I see, I get what you mean and you are right. No need to make any changes to the Simple sensor item' label.
  5. BHSY
    Thank you so much for implementing the 'Change Souce'.🩷 Everythings works as we hope, especially the min/max values were retained as it was. However, the sensor description did not change. Please refer to the IMAGE 1 below, I have duplicated all the CPU sensors and change them to GPU sensors. However, the description still shows as CPU. It should changed accordingly to the 'Item type' in the Modify Item. Add: Is it possbile to select all the same 8 custom sensor gauges and change them all at once, instead of one at a time? As for the IMAGE 2, the item type is a 'Simple sensor item'. I duplicated the CPU Utilization and change it to GPU Utilization but the description still showed as CPU Utilization. The only way for me to change the description is to enable the 'Show label' and type in GPU Utilization. Also, I think it is better for the 'Show Label' to changed too when we change to a different sensor, regardless if the 'Show Label' was enable or disable? Thank you!
  6. BHSY
    Cool. Looking forward to it. Thank you🙏.
  7. BHSY
    Thank you for working on this new feature😉 As Surjeet mentioned, it all depends on the user’s specific use case. If a user chose to show the label on their layout, it would be convenient and time-saving for them if the label could be changed accordingly when selecting a different sensor. Still, a user might use a different label, for example, he chooses to use 'Utilization' instead of 'CPU Utilization'. So, not just to retain the min/max value, the label should be retained as well, if can. For me, I don't usually use the label so if I replaced a different sensor, the label shouldn't appear on my layout. The most important part is that the min/max values are preserved when replaced with a new sensor, especially for usage and temperature. I also use a different value for a 15 state (a single custom gauge sensor). For example, the CPU temperature minimum value is 80 and the maximum is 100. This is to alert the user if the CPU temperature reaches around 80 degrees, a bright red LED image will appear on the panel.
  8. BHSY
    I like this idea. The 100 states (a total of 8 sensors) contain different min/max values. If the value can be retained without reverting to its default value when selecting a different sensor, for example, changing CPU temp to GPU temp, I would like this feature implemented. If not, there is no point in using the REPLACE shortcut. The REPLACED shortcut would be useful for other sensors that don't require the 100 states sensor.
  9. BHSY
    I'm not sure which images you're referring to but for me, if I create an image, I will not change the default size and resolution. This will make the file size bigger. Let's say I'm currently using a 1080p monitor with a 100% display scale and I created an image size of 200x200, 75 dpi for my 1920x515 sensor monitor. I have also input the image 'Resize' as 200x200 in the Modify Item. Now I've upgraded to a 4k/2160p monitor with a display scale of 150%, and AIDA64 enlarged the image size. The image might look a bit blurry on a 150% display scale but if I shift the sensor panel to my 1920x515, which is 100% display scale, it will look normal and perfect. For me, there is no need to increase the default image size and resolution and the file size won't be so huge either. I hope you understand what I have mentioned.
  10. BHSY
    If I understand correctly, the scale menu is to scale all items up, not to scale them back down. However, it would be good to scale down. @Fiery, is it possible to implement an option to scale all items down after scaling them up? This would be useful for us to check if we miss any of the images without the resize option, instead of switching our resolution back to 100% display scale.
  11. BHSY
    I see. I understand now. I just tried and it works. Thank you for your explanation.
  12. BHSY
    I just emailed you. Thanks.
  13. BHSY
    I downloaded the latest Beta Version: 7.99.7805 beta (Jun 04, 2025) that scales all items up by 125%, 150%, 175%, or 200%. I tried it on my 4k monitor with display scale 150% and it works great, everything scales up to 150% without enabling the 'Change high DPI settings. However, there is one issue: sensors that use blank PNG don't scale up on my primary monitor. I tried it on my panel and AIDA64 default skin, which has no blank PNG file, works flawlessly. Purpose for using a blank PNG: To centralise the sensor items by using custom gauge, for example, 11%, 38°C To create a dial gauge that uses 8 sensors (I love dial gauge very much) Can you fix or include the scales up for the blank PNG?🥹 Thanks. @Fiery @COSTAJUNIOR @pcrepairvk @Exhumed @JariKoi @Surjeet
  14. BHSY
    Hmmm....A HEX code will be useful to me. I don't have to remember 3 separate codes like the RGB, just copy and paste the HEX codes from Illustrator or Photoshop. I, too, opt for the colour picker from Windows Paint as mentioned by @Surjeet, the Hex code input was placed as the first choice to enter the colour code. Also, we can save custom colors, which is important.
  15. BHSY
    Oh WOW!😮 I did not expect the export preview thumbnail to be released so soon. I've tested it and it shows my thumbnail. Well done💪, Fiery, and thank you so much!🙏
  16. BHSY
    Thank you🙏. The drop-down list is simple and clean. Better than I expected👍.
  17. BHSY
  18. BHSY
    If using the snapshot is going to cause an increase in the SPZIP file size, then I prefer to do it manually by adding a preview.jpg in the SensorPanel Manager and hiding it. If not, there's no point in using SPZIP. By adding the preview.jpg ourselves, we can manually set the preview file size we want, as long as the thumbnail is viewable. No need for further complicated options or changes. Option A is better✅, don't change it. Option B seems like a lot of work to me so definitely a no❌.
  19. BHSY
    Oh WOW! That is so great.☺️ Look forward to your next beta update. I forgot to mention that now I can finally stress test my ASUS TUF GAMING RTX 5070 TI GPU Card using the System Stability Test. Thank you🙏.
  20. BHSY
    I got it after reading the above post. I set my preview.jpg as a hidden image in SensorPanel Manager. Thank you🙏. Is it possible to show a thumbnail preview when I want to export the file? What I mean is, after creating or saving a new SPZIP file with the preview.jpg or preview.png placed in the SensorPanel Manager, show a thumbnail preview under the "*.spzip already exist. Do you want to replace it?" when we want to overwrite the same file again, to make sure we overwrite the correct file. Below image is an example:
  21. BHSY
    Yes, both. import and export to show the thumbnail preview. Sorry, I wasn't clear enough.
  22. BHSY
    That is a great idea, I like it. I don't mind if it is a preview.jpg or preview.png, as long as the image is clear and doesn't slow down the loading time of the thumbnail. What about overwriting the old file? Is it possible for the dialog box to preview the old file image before we click Yes to overwrite it? There were a few times I accidently overwrite the wrong file. Luckily, I have a back up file and a zip file.
  23. BHSY
    I see, I get it now. Yes, get rid of the left-click to cycle between pixel strides and use the drop-down menu to select the px. If you can, please also add a shortcut px selection on the context menu too. Thanks.
  24. BHSY
    I am glad to hear that😮‍💨. Thanks. Do you mean something like this? If yes, please go for it. Will the directional and pixel buttons will be removed? I have no issues with that but I can't say for new users, they might not know about the Alt-arrow key to move the items. Is it possible to retain them?
  25. BHSY
    Keyboard-based navigation (Alt+arrow key) is very useful for me, so please don't ever remove it😊. To me, using 2 navigation blocks can be confusing, I might select the wrong block. Often, I over-clicked the pixel selection button twice and I have to click it all over again😤, so it is a great idea to have a right-click menu to select the pixel I want, once. I prefer the right-click menu instead of clicking the px button repeatedly. For me, 1px, 5px, 10px, 20px, 50px, and 100px is sufficient for me. I vote for having a right-click menu to select the px stride, please😊. Thank you.
×
×
  • Create New...