Batch Rename wildcarding not working/consistent with WIndows console wild card matching conventions

[GoogleCodeExporter]

What steps will reproduce the problem?

I have a folder containing files named:

Part 1.1.1
Part 1.1.2
Part 1.1.3
Part 1.1.4
:::
Part 1.1.30

These files are jpg images that were saved from an email without a proper .jpg 
extension. In the past I have renamed them using the console window and typing 
in:

rename *.*.*  *.*.jpg

I would expect to have the same result using the StEx batch rename function but 
- it doesn't work.

1. Click batch rename icon in explorer window
2. In Rename dialog, Match entry type:  *.*.*
3. In Rename dialog, Replace entry type:  *.*.jpg

What is the expected output? 

I expect the renamed side to show the predicted new name with a .jpg extension 
based on what I entered in the Replace pattern.

The list of filenames matching the match entry in the Match column and the 
renamed column showing the predicted new name ending with the extension .jpg

What do you see instead?

I see the list of filenames matching the match entry in the list below however, 
the left 'filename' side and the 'renamed' side are exactly the same. No matter 
what pattern I enter in the Match and Replace fields - nothing changes in the 
list.

Just for grins I clicked the Rename button anyway and nothing happened.

What version of the product are you using? 

1.8.3.352

On what operating system?

WinXP SP3

Please provide any additional information below.

I am able to type rename *.*.* *.*.jpg directly into the StEx console entry 
field on the explorer window and the files are renamed correctly.

BTW, nice feature having a console window entry field on the explorer window as 
it provides a work around to the batch rename failure that I am reporting here.

Original issue reported on code.google.com by b...@digilink.net on 8 Jun 2012 at 5:15

[GoogleCodeExporter]

The rename feature uses regular expressions which are incompatible and 
definitely not the same as windows wildcard matches.

Regular expressions are much more powerful than wildcard matches, that's why 
they're used in the rename feature.

But that's documented.

Which means: this is by design!

Original comment by tortoisesvn on 8 Jun 2012 at 5:20

• Changed state: Invalid

[GoogleCodeExporter]

My bad - I just assumed Windows wildcard conventions. RE definitely provides a 
more powerful functionality.

Original comment by b...@digilink.net on 10 Jun 2012 at 3:45