I am sure what I am about to describe is a feature. However, it
creates additional work, and I think the program could be smarted
about the situation. Here's an example.
Create a dialog with 2 bitmap buttons: BBIT1 and BBIT2. Add 2
graphics to the buttons. p1.png and p2.png. Use the Copy into
function. Assign the png files to the buttons. Everything is good to
this point.
Now, you want to update p1.png. If you delete it from the images list
and then attempt to add it, DB changes the name to p11.png (appends a
1). Then when you build, the button looks for p1.png, and it's not
there. So, you fix this by doing the following: 1. before you load a
new p1.png, delete the reference to it; 2. add the image.
This works for a while. At some point, this process doesn't work, and
the graphic files have a 1 appended to the base name even though there
is no reference to the image name. At this point, you have to quit DB
and start again. In a restart of the program, you can add the graphic
file without any problems.
I can see where the DB authors would not address the 1st point.
However, the second one should be address in a future release.
Peter
.