fixed: Gauge Bug – State #0 Name Cut + Icon Changed (Latest Update)

[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.

 

[Fiery]

1 hour ago, COSTAJUNIOR said:

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.

 

Do you select the 16 states (in your first example) in a single round by selecting 16 files in the file open dialog?  We've tried that but couldn't reproduce the bug

As for the state icon, that is due to a limitation of the new compiler.  We had to remove it to avoid visual issues to occur.  We'll try to find a way to put it back or find another way to indicate the SensorPanel item type (e.g. gauge) as well as the sensor type (e.g. temperature) in the same chart cell.

[COSTAJUNIOR]

7 minutes ago, Fiery said:

Do you select the 16 states (in your first example) in a single round by selecting 16 files in the file open dialog?  We've tried that but couldn't reproduce the bug

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. 😔

[Fiery]

Just now, COSTAJUNIOR said:

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. 😔

Even if you only alter the first state by selecting a single file, the filename still gets cut?

[Fiery]

20 minutes ago, COSTAJUNIOR said:

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. 😔

We could finally reproduce the bug.  It seems to be only a visual issue.  In other words, even though the filename looks cut, the actual filename is properly used by the custom gauge.  We will still fix the issue of course

[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! 😊

[Fiery]

2 hours ago, COSTAJUNIOR said:

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! 😊

Funnily enough, this one seems to be a compiler bug that we cannot fix on our end.  Apparently there's a 78 character limitation on the caption of the very first item in popup menus.  What we can do is add a header to the popup menu as a workaround.  We will also report the compiler bug to Embarcadero.

[Surjeet]

15 hours ago, COSTAJUNIOR said:

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! 😊

Thank you @COSTAJUNIOR for bringing this up. I also faced the same issue. However, good to know that even with the Name-Cut, the functionality was not hampered. Custom gauges worked as per the images added.

13 hours ago, Fiery said:

Funnily enough, this one seems to be a compiler bug that we cannot fix on our end.  Apparently there's a 78 character limitation on the caption of the very first item in popup menus.  What we can do is add a header to the popup menu as a workaround.  We will also report the compiler bug to Embarcadero.

Thank you for addressing this and we will love to see how the workaround = popup menu is implemented!! Thank you once again!

[Fiery]

On 6/4/2025 at 3:52 PM, COSTAJUNIOR said:

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.

@Surjeet

We've fixed both issues in the latest beta version of AIDA64 Extreme available at:

https://www.aida64.com/downloads/latesta64xebeta

[Surjeet]

1 hour ago, Fiery said:

@Surjeet

We've fixed both issues in the latest beta version of AIDA64 Extreme available at:

https://www.aida64.com/downloads/latesta64xebeta

WOW, Once again what a fast turnaround!! 😍

I confirm that the issue is resolved and in addition, now we can see custom gauge icons clearly too!!

Thank you!!!!!

On a side-note, all creators have posted their reply with their preferences in this forum. We are just curious to know if we will have something interesting coming 🙂

 

 

[Fiery]

3 minutes ago, Surjeet said:

WOW, Once again what a fast turnaround!! 😍

I confirm that the issue is resolved and in addition, now we can see custom gauge icons clearly too!!

Thank you!!!!!

On a side-note, all creators have posted their reply with their preferences in this forum. We are just curious to know if we will have something interesting coming 🙂

Thank you for your feedback!  I've responded in the HEX code topic too.

[COSTAJUNIOR]

7 hours ago, Fiery said:

@Surjeet

We've fixed both issues in the latest beta version of AIDA64 Extreme available at:

https://www.aida64.com/downloads/latesta64xebeta

I updated to the latest beta version and everything is working perfectly. I appreciate how quickly and reliably you always address and fix issues. 😉

[Fiery]

6 hours ago, COSTAJUNIOR said:

I updated to the latest beta version and everything is working perfectly. I appreciate how quickly and reliably you always address and fix issues. 😉

Thank you for your feedback!  We keep pushing hard to polish out the remaining issues in the next-generation AIDA64 beta channel.