Quote:
Originally Posted by DiapDealer
And yet epubs are validated without any errors all the time by the integrated Flightcrew. So we're missing something. As written... yes, there will be an exception and an error, but the snippet of code doesn't tell us when; under what circumstances; or even IF that code gets called.
|
No, that method does not get called from the integrated code. I read that, and it uses an already opened ePub directory via this method:
FC_WIN_DLL_API std::vector< Result > ValidateEpubRootFolder( const std::string &root_folder_path );
Which works great when I tested it myself. I'm just wondering what the story is with the other method.
I'm interested in this because I'd like to have a flight crew command line executable again, but don't know the code base very well, yet.
Thanks