[bt-devel] Module Install error handling

[Eeli Kaikkonen]

On Fri, 19 Jun 2009, Greg Hellings wrote:

> I'm testing out my latest build of 2.0.1 on fresh install of Vista and
> was happy to see the module install manager alert me that the
> directory I was about to install to was "unwritable or does not
> exist."  In my case, it didn't yet exist, being C:\Users\Greg\.sword.
> I'm fairly certain that QDir has methods to test both the writability
> and the existence separately.  Would it be a bad thing to test for
> existence and, if it doesn't exist, test that it COULD be created and
> prompt the user to create it.  If, on the other hand, it can't be read
> at all, then providing an error message to simply state that?  I'd be
> willing to dig through the code and find that, after I get this build
> out into the wild.

If it helps the user and works under all circumstances, it's good.

> At the same time, I'd like to eliminate the usage
> of dirent.h in the one file where we use it, since for me on Windows
> it perennially presents a snag to configuring and building that needs
> special manual attention.  I've looked through that code and am
> certain it can be rewritten with Qt classes to do the testing -- any
> objections to me doing that?  It would save some hassle on the Windows
> build side, and remove our dependence on that non-crossplatform file
> dirent.h.

I think we have had some discussion about this specific file. It's
usually better to use Qt if it's not too complicated. It's only good if
we can get rid of extra dependencies.

  Yours,
	Eeli Kaikkonen (Mr.), Oulu, Finland
	e-mail: eekaikko at mailx.studentx.oulux.fix (with no x)