If we are going this way I agree with Steffen:
w.
Steffen Wrote:This part creates a precedence case which needs to be resolved:
The XXXXh.dat file models a different virtual version of XXXX.dat,
but in reality only ONE such part existed AFAIK.
I don't think that it is a Good Idea ™ to have to virtual
representations of the same part in our library.
Either XXXX.dat or XXXXh.dat has to be deleted.
The remaining part then has to get the normal file number XXXX.dat
again. The "h" suffix does not make much sense to me.
The reason for creating the two variants probably was
to leave the decision to the user if he wants a detailed baseplate
underside or not. But I think that that issue should be resolved
not by this special "h" suffix, but instead the same way
as the "coarse" studs had been implemented:
all baseplates should be modeled with detailed underside,
and the underside negative stud could be present in two versions,
a detailed one, and a simplified one - i.e., one that isn't present
at all and models the underside as flat as previously.
w.
LEGO ergo sum