Jump to content

fixed: Serious bug with custom gauges


Go to solution Solved by rinaldop,

Recommended Posts

Posted

If you export a .sensorpanel file with any custom gauge hidden when you import the same panel back in the custom gauges that were hidden will now be corrupt. The paths to the image file become corrupted. I tried this with several different custom gauges and it happened every time. I wasted HOURS trying to track down the cause of my panels becoming corrupted.

I tested versions beta 7.00.6738, beta 700.6742, and stable 7.00.6700

Here is an image of the paths error.     

 

Screenshot 2024-02-18 151703.png

Posted (edited)
  On 2/18/2024 at 10:06 PM, rinaldop said:

If you export a .sensorpanel file with any custom gauge hidden when you import the same panel back in the custom gauges that were hidden will now be corrupt. The paths to the image file become corrupted. I tried this with several different custom gauges and it happened every time. I wasted HOURS trying to track down the cause of my panels becoming corrupted.

I tested versions beta 7.00.6738, beta 700.6742, and stable 7.00.6700

Here is an image of the paths error.     

 

Screenshot 2024-02-18 151703.png

Expand  

I support this finding as I have also faced the same issue multiple times!

Here is my screenshot of the issue:

image.jpeg

 

Edited by Surjeet
Added Screenshot
  • Like 1
Posted
  On 2/19/2024 at 4:32 PM, rinaldop said:

Excellent! Thank you for confirming this so I know it is not my system. 

Expand  

We've already fixed that in the latest AIDA64 beta build, but maybe your existing layout already includes the incorrect paths.  Try to manually fix the paths and check if it works now with the export-import process.

Posted
  On 2/20/2024 at 1:08 PM, Fiery said:

We've already fixed that in the latest AIDA64 beta build, but maybe your existing layout already includes the incorrect paths.  Try to manually fix the paths and check if it works now with the export-import process.

Expand  

I did a brand new install of Aida64 then installed v7.00.6742 Beta. I imported a previous panel that contained custom gauges, hid only one custom gauge, then exported the file. I then imported the file and the hidden custom gauge had the file paths corrupted, the other gauges were fine.

The problem still exists.   

Posted
  On 2/19/2024 at 11:51 AM, Surjeet said:

I support this finding as I have also faced the same issue multiple times!

 

Expand  

Supposedly the bug has been fixed in the latest Beta, but the bug is still there for me in version v7.00.6742 Beta.

Will you try it and see if it works for you?

Thanks!  

Posted
  On 2/20/2024 at 5:50 PM, rinaldop said:

I did a brand new install of Aida64 then installed v7.00.6742 Beta. I imported a previous panel that contained custom gauges, hid only one custom gauge, then exported the file. I then imported the file and the hidden custom gauge had the file paths corrupted, the other gauges were fine.

The problem still exists.   

Expand  

What I mean is that the existing layout has the gauge state paths already corrupted, and the new beta exports it and imports it back without altering the corrupted paths.  But, if you could kindly send us the AIDA64.INI file with your existing SensorPanel layout, we could try to reproduce the issue.  Quite honestly we've fixed the issue already, but maybe it doesn't work properly in all cases.

Posted
  On 2/20/2024 at 7:05 PM, Fiery said:

What I mean is that the existing layout has the gauge state paths already corrupted, and the new beta exports it and imports it back without altering the corrupted paths.  But, if you could kindly send us the AIDA64.INI file with your existing SensorPanel layout, we could try to reproduce the issue.  Quite honestly we've fixed the issue already, but maybe it doesn't work properly in all cases.

Expand  

Fiery,

I used a fully functioning gauge without any path corrupted. Give me some credit for having common sense. 

Posted
  On 2/19/2024 at 11:51 AM, Surjeet said:

I support this finding as I have also faced the same issue multiple times!

Expand  

Supposedly the bug has been fixed in the latest Beta, but the bug is still there for me in version v7.00.6742 Beta.

Will you try it and see if it works for you?

Posted
  On 2/21/2024 at 7:01 AM, rinaldop said:

Supposedly the bug has been fixed in the latest Beta, but the bug is still there for me in version v7.00.6742 Beta.

Will you try it and see if it works for you?

Expand  

Sorry for the delayed response as I was away.

I tried the beta with fresh panel (wherein path was not corrupted) and I was unable to reproduce the issue again.

Its intermittent and it happened to me last time when I saw your message and it was a coincidence. I updated that screenshot here earlier too as that error did come.

I would update it again if it happens again while I am trying to reproduce the issue. You also keep on trying and report if you face it again!

Posted
  On 2/21/2024 at 9:40 AM, Surjeet said:

Sorry for the delayed response as I was away.

I tried the beta with fresh panel (wherein path was not corrupted) and I was unable to reproduce the issue again.

Its intermittent and it happened to me last time when I saw your message and it was a coincidence. I updated that screenshot here earlier too as that error did come.

I would update it again if it happens again while I am trying to reproduce the issue. You also keep on trying and report if you face it again!

Expand  

Thank you for trying!  

This is the WORST kind of bug to fix, one that is INTERMITTENT! I am trying to debug this with Fiery in email and he keeps telling me that my gauge is corrupted BEFORE I try the export/import test.  I was hoping that you still had the problem also since now it seems that I am the only one having the bug.

I will keep trying and see what happens. 

 

  • Thanks 1
Posted
  On 2/21/2024 at 4:49 PM, rinaldop said:

Thank you for trying!  

This is the WORST kind of bug to fix, one that is INTERMITTENT! I am trying to debug this with Fiery in email and he keeps telling me that my gauge is corrupted BEFORE I try the export/import test.  I was hoping that you still had the problem also since now it seems that I am the only one having the bug.

I will keep trying and see what happens. 

 

Expand  

You're absolutely right, this is a nasty bug that was supposedly already been fixed in the latest beta build, but actually kept rearing its nasty head up still :)  We will fix it hopefully once and for all in the next AIDA64 beta update due next week.  Thank you for helping us track it down.

  • Like 2
Posted
  On 2/21/2024 at 7:57 PM, Fiery said:

You're absolutely right, this is a nasty bug that was supposedly already been fixed in the latest beta build, but actually kept rearing its nasty head up still :)  We will fix it hopefully once and for all in the next AIDA64 beta update due next week.  Thank you for helping us track it down.

Expand  

Thank you for saying that I was right, I knew that there was nothing wrong with my gauges before I did the test;)

  • Fiery changed the title to fixed: Serious bug with custom gauges

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.



×
×
  • Create New...