Though eType's validity is mostly tracked with nCount being non-zero
this is not so for the case (!bImage && bHasColor)
Initializing eType properly solves all cases for good, gets rid of the
subtle validity semantics and shuts up the compiler+testtool warning