Jump to content

COSTAJUNIOR

Sensor Moderators
 View Profile  See their activity

  • Posts

    515

  • Joined

  • Last visited

  • Days Won

    97

 Content Type 

Everything posted by COSTAJUNIOR

  1. COSTAJUNIOR
    Okay, I don't speak English, so I have to rely on translators, which never manage to interpret my ideas correctly πŸ€¦β€β™‚οΈ. In the end, all I can do is sit with a bag of popcorn 🍿, waiting for another update that will surely turn out amazing πŸ˜…βœ¨.
  2. COSTAJUNIOR
    Wouldn't it be simpler to keep access the same as it is in the current palette? Clicking on a color would open the new selection box with all the new features built in.
  3. COSTAJUNIOR
    Perfect 😍, this update is very well on track and represents a big leap in usability. Switching to the MS Paint color set was a great choice, and the compatibility with the GPL format makes things much easier for those who work with custom palettes. The ability to easily save and load colors is a major plus. The new patch size (18x18px) with borders makes everything cleaner, more functional, and pleasant to use β€” especially with the automatic scaling based on Windows settings. That ensures accessibility in all scenarios. The only thing that still bothers me a little is having to use the right mouse button to access the new color palette. I hope to see it available more directly, without relying on that shortcut. That said, the recent colors system looks great, and the palette customization method is clear and intuitive. Keep up the great work β€” the refinement is looking impeccable! πŸ˜‰
  4. COSTAJUNIOR
    🟑 Radiation Protocol - in 1024x600 and 1920x480 ⚫ This skin was forged in the core of a fictional nuclear reactor β€” post-apocalyptic aesthetic, industrial vibe, and visuals inspired by radioactive containment panels. Every detail crafted for those who crave extreme monitoring with a brutalist flair. πŸ”₯ Features: Full monitoring for CPU and GPU (temperature, load, voltage, power draw, fan speed, RAM/VRAM usage). Analog gauges styled after industrial emergency dials. Storage indicators with custom SSD icons. Nuclear-themed visuals with radiation icons, worn metal textures, and glowing green/amber tones. The "High Temperature" nuclear symbols dynamically reflect the CPU (left) and GPU (right) temperature states. Discover this and other models at: [AidaSkins]
  5. COSTAJUNIOR
    1) Yes, a single custom palette like in MS Paint is perfectly fine. Having Save and Load options is enough to give flexibility. 1/b) No, I don't see the need for multiple palettes with tabs at this point. I prefer keeping the interface simple and focused, with just one customizable palette. 2) 24 custom colors is a good number. It's a balanced amount β€” not too many, not too few β€” and it keeps things organized. 3) If possible, using a standard format like .ASE (Adobe) or .GPL (GIMP) would be great for compatibility. But if it's easier to create a custom format, that's fine too β€” as long as it's easy to read and edit. 4) Yes, naming the custom colors would be very helpful. It makes it easier to identify specific colors used in a project. 5) Yes, a right-click context menu on the color patches (like in the SensorPanel item configuration) would be very useful. It would save time by allowing quick access to saved colors without opening the entire color picker dialog. 6) 10 recent colors would be ideal. That gives good recall without taking up too much space. 7) 20x20 px would be a better size than the current 16x16 px. Slightly larger patches β€” like the 20 px circles used in MS Paint β€” would improve usability, especially on high-DPI or 4K screens.
  6. COSTAJUNIOR
    Hey! I also found the idea interesting and fully support the implementation of this new feature. I've developed a few projects in this style, but I noticed that the saving process became quite slow due to the large number of states created.πŸ˜‰
  7. COSTAJUNIOR
    Wow! 😍 Once again, you’ve surprised us with these amazing updates. Congratulations on fulfilling yet another one of our requests β€” it really shows your care and attention to the community. I'd like to take the opportunity to suggest a few improvements, if possible. Customizable and Saved Color Palette: Managing custom colors is essential. Being able to save, name, and even export/import palettes would help a lot, especially for those who create multiple skins and need to maintain a consistent visual identity. Recent Color History: A small history of recently used colors would also make a big difference in the creative workflow. Also, it would be great to make the new panel more intuitive. I’m not sure if the old version will be replaced when this one is officially released, but removing the need for a right-click to access the new color picker would definitely improve the usability. A more accessible and straightforward interaction would benefit all users. πŸ‘ŠπŸ˜‰
  8. COSTAJUNIOR
    Man… I don’t even know where to start. This update turned out crazy good! I tested it with 101 states and the result was insane β€” seriously, you nailed it. Congrats on the work, it’s getting better and better, and huge thanks for always listening to us and delivering more than we expect. I N C R E D I B L E. No exaggeration. 😍 😍 Now, just one question: with this change, does the β€œChange Source” option still make sense, or did it lose its purpose?
  9. COSTAJUNIOR
    I agree with @BHSY. Keeping the original 15 states intact is essential so it doesn’t affect the sensors that have already been created. But it would be amazing to have new options like 30, 50, and 101 states β€” that would open up a huge range for creating even more personalized and detailed sensors. It would be a major step forward in customization!
  10. COSTAJUNIOR
    Thanks, it looks perfect! πŸ˜€
  11. COSTAJUNIOR
    I managed to find the function. It was actually there all along β€” the trick is to right-click on the sensor you want to change and select the Change Source option. I was double-clicking instead, which is why that option never showed up.😁 I’d like to suggest an improvement: when selecting Change Source, the system should display all available sensors, not just those in the same category. For example, if I click on a CPU temperature sensor, it only shows other temperature-related sensors. This really limits customization. Another important suggestion: it would be great to have an option to select multiple sensors at once and apply changes to all of them automatically. That would save a lot of time instead of having to update each one manually.
  12. COSTAJUNIOR
    Thank you again for the update. However, in my case, it had no practical effect, even after applying it. When I replace a sensor β€” for example, switching the CPU temperature sensor to the GPU β€” the minimum and maximum values are not preserved. I'm specifically referring to the use of sensors with 100 states distributed across 8 custom sensors. I would also like to suggest adding the option to select all 8 custom sensors at once and change them simultaneously, instead of having to modify each one individually.
  13. COSTAJUNIOR
    Thanks a ton for always responding so quickly and bringing these awesome improvements to the community. Can’t wait to try out the next beta! Now all that’s left is that legendary update everyone’s dreaming of: the glorious animated GIF! πŸ˜‚πŸ”₯
  14. COSTAJUNIOR
    Absolutely, I’m fully on board! For setups using 100 states across 8 sensors, this would definitely make a huge difference. Keeping the minimum and maximum values preserved when switching sensors isn’t just convenient β€” it’s essential for anyone managing complex layouts. It saves time, reduces errors, and makes the whole process much smoother. πŸ‘Š
  15. COSTAJUNIOR
    I’ve been following along, but it’s very confusing to me. @Fiery @BHSY, @Surjeet, I opened the sensorpanel_default.spzip file and the images are sized at 896x896 pixels with a resolution of 288. To ensure all scales work correctly without errors, do we need to create the gauges at this resolution?
  16. COSTAJUNIOR
    I updated to the latest beta version and everything is working perfectly. I appreciate how quickly and reliably you always address and fix issues. πŸ˜‰
  17. COSTAJUNIOR
    Here you will find several models. https://forums.aida64.com/search/?q=600x1024&quick=1&type=forums_topic&item=13296
  18. COSTAJUNIOR
    Perfect, thanks for the update! Glad to hear you were able to identify the bug. Even if it’s just visual, it’s good to know the internal functionality is working correctly. Looking forward to the fix β€” thanks for the continued effort! 😊
  19. COSTAJUNIOR
    Yes, I’ve already tried everything. I even tested it with older sensors that used to work fine, and the issue is still happening. So it doesn’t seem to be related only to the current method, which makes me wonder if this problem is only happening to me. πŸ˜”
  20. COSTAJUNIOR
    After this latest update, I noticed a bug when creating a custom gauge: the first entry doesn’t show the full name, as you can see in the image. It should appear like this: bar-reactor-down_0 (gauge with 16 states). The same thing happens when I create a gauge with 8 entries and 100 states β€” always on state #0. For example, the name should be reactor-control-cpu_00, but it’s getting shortened, as shown in the image. This issue only happens with state #0; all other states remain correct. Another thing I noticed: when creating a new gauge, the icon is no longer the old circle shape. Now it appears with the same icon as the sensor β€” in my case, the processor icon. Was this change intentional? Will it stay this way? I really preferred the old icon because it made it much easier to visually identify the gauges.
  21. COSTAJUNIOR
    I really like the color dialog in MS Paint, mainly because of its simplicity and the direct access to the custom color palette. It would be great to see something along those lines! Additionally, I’d like to suggest testing the implementation directly in Windows Paint, to observe how it behaves in a real and widely used environment. It would serve as a great practical reference to validate usability and clarity. Hexadecimal color support would be extremely important to ensure precision in color selection, especially in contexts where visual fidelity is essential. πŸ‘Š
  22. COSTAJUNIOR
    I tested it just like you explained, and it's definitely much more practical and faster! I added "Preview.jpg" as the first item in the sensor panel, hid it, exported the SPZIP, and the preview image showed up perfectly when importing. I'm going to use this method from now on β€” way more efficient. And an important note: there's no need to save the "Preview.jpg" at maximum resolution. Using the High option already gives great quality for the preview without making the SPZIP file too heavy. Congrats on the tip β€” that was pure gold!
  23. COSTAJUNIOR
    I didn't quite understand, but the idea was to implement everything directly within AIDA64, including a button to load the 'preview.png' image. When exporting the skin, this file would be automatically included in the .SPzip package generated by AIDA.
  24. COSTAJUNIOR
    I would like to congratulate the entire team. I have tested the new image preview feature during sensor import, and I can confirm that it is working flawlessly."
  25. COSTAJUNIOR
    Thanks a lot! I found out that the files aren't showing their extensions. It only shows 'aida64
×
×
  • Create New...