Closed dpogue closed 11 months ago
Not something that needs to be done in this PR, but I think it would make sense to pull hsMessageBox
out into its own header. Possibly even into another library, somewhere under PubUtilLib. If my search is correct, hsMessageBox
isn't called anywhere in CoreLib or NucleusLib, so it would be great if we could build those libraries without depending on GUI libraries for no reason.
I think it would make sense to pull
hsMessageBox
out into its own header. Possibly even into another library, somewhere under PubUtilLib.
I like this idea
hsMessageBox
that take ST::stringI'm unsure on whether it makes sense to change the hsMessageBox stuff to always convert to ST::string and then have a single implementation, or if it's more performant having it split up as it currently is...