@20: "You need to restart the application after removing the files (and
all other files with the same TTHs) from share before performing
rebuild."
That's the problem right there. Files one has moved and/or renamed but
that are still shared shouldn't need to be deleted (or moved out of the
share) c
"Of course your motive is to make it easy to move *to* Air and not away
from it (hence the import feature for the old DB format), but still..."
My motivation was to make it possible for people using older versions of
the application to upgrade without losing their data...
Regarding comment #14:
@maksis: TBH I'm not completely averse to the changes made, but the only
issue is how they're specific to Air. Given the advantages one would
have expected the changes to have been introduced upstream rather than
have Air diverge from all other DC++ clients. Perhaps an attempt was
even made in this
You make it sound like the file formats have been changed without proper
reasons. No, the hash database format wasn't changed because of this
issue (I just wanted to report my findings here while making the
rewrite). Dealing with a hash index XML file that could be several
gigabytes in size and bei
@eMTee (realprogger): Thank you for pointing me to dcbase.org; I was
unaware of that site.
Re. AirDC++, that is indeed one of the clients I'm actively considering
switching to, esp. since it's the only one whose developer(s) still seem
to be be around to respond to queries and hopefully fix bugs a
@Davidson: I think you answered your own questions yourself. If this
problem hits you hard then instead of waiting I'd rather suggest
switching to AirDC++.
This bug thread isn't the right place to discuss the DC++ development
though so if you have further questions or thoughts then please use the
6 matches
Mail list logo
