Editing existing harddrive path for DH0: in GUI changes Amiga drive definition?

[giantclambake]

Premise: This only became apparent after the Harddrives placeholder was added.

Synopsis: Users may have existing config.uae files that contain harddrive definitions. If when users upgrade to a later version of amiberry that provides the Harddrives placeholder, they have a few options...

-do nothing, leave existing harddrive media where it is, and the config.uae files remain valid.
-change the Hard drive path: to suit their existing setup (config.uae files may remain valid)
-move existing harddrive media into the Harddrives directory to take advantage of that placeholder

If they do that latter, the config.uae files will no longer be valid, and need to be edited to define the new harddrive location(s).

At this point, user has a couple of choices -- manually edit the config.uae files ...or... use the GUI to effect changes.

When it comes to using GUI->Hard drives/CD panel to make required changes, user has 2 choices;

-click on the 'X' (cross) to delete existing harddrive path, then click on the '...' button to re-add correct path.
-click on the '...' button to alter the path ..this is probably the quickest route, as it opens in the Hard drive path: location.

Following the latter route, changing path for DH0: results in it being displayed as DH4: ... https://youtu.be/_ZYj6DUOfYM

I think it's just in the GUI somewhere, as the resultant config.uae file seems to be correct (caveat mention of DH4:)....

hardfile2=rw,DH4:/home/gcb/Amiberry/harddrives/hdf/CWB-P96.hdf,32,1,2,512,0,,uae0
uaehf0=hdf,rw,DH4:/home/gcb/Amiberry/harddrives/hdf/CWB-P96.hdf,32,1,2,512,0,,uae0
filesystem2=rw,DH1:ClassicWB:/home/gcb/Amiberry/harddrives/disks/ClassicWB,-127
uaehf1=dir,rw,DH1:ClassicWB:/home/gcb/Amiberry/harddrives/disks/ClassicWB,-127
filesystem2=rw,DH2:HDD:/home/gcb/Amiberry/harddrives/disks/HDD,0
uaehf2=dir,rw,DH2:HDD:/home/gcb/Amiberry/harddrives/disks/HDD,0
filesystem2=rw,DH3:WHDload:/home/gcb/WHDload,0
uaehf3=dir,rw,DH3:WHDload:/home/gcb/WHDload,0

...that is to say the uaehf# definitions are correct, and thus the emulation still sees that drive as DH0: irrespective of how the GUI is describing it as being DH4: ?

TIA