On 2 May 2010 12:23, Brendon Higgins <[email protected]> wrote: > This bug is really only half fixed. The wording of the message is a bit > clearer now, though it could be improved if the answer was "Yes | No", for > example, rather than "OK | Cancel". Cancel implies cancelling an operation in > progress (i.e. the program itself - this was my original interpretation of > the message), rather than denying a proposed action. > > But also, the regex the program is using to detect whether slices of old > archives exists catches too many cases. Again I was in the situation where I > had an archive titled such as "example.large" transforming to "example". > dar_xform has no need to complain about this situation. I can only presume > the regex is parsing the ".large" part of the name as the slice number, > rather the real slice number that immediately follows it.
Hello, Can I please get you to follow up on this bug at the upstream website? http://sourceforge.net/tracker/?func=detail&aid=2970084&group_id=65612&atid=511612 I think that way it can get solved faster then if I relay comments between the two BTS systems. Thanks! -- Brian May <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
