-loadframes not expanding wildcard filenames into multiple args

[GoogleCodeExporter]

Hi:  I don't know whether you even want these.

What steps will reproduce the problem?
1. imagestack -loadframes foo*.jpg

What is the expected output? 
I expected it to load a sequence of frames from the files (foo0001.jpg , 
foo0002.jpg, ...)

What do you see instead?
Performing operation -loadframes foo*.jpg
Could not open file foo*.jpg

What version of the product are you using? On what operating system?
imagestack version 2010-7-31 Win64
on 64bit Win7

Please provide any additional information below.
Perhaps sequence loading is not yet implemented in LoadFrames::parse()?

Original issue reported on code.google.com by Terry.Th...@gmail.com on 11 Oct 2010 at 5:14

[GoogleCodeExporter]

From looking at the documentation I was expecting loadframe to expand foo*.jpg 
to (foo0001.jpg , foo0002.jpg, ...).  However, the functionality as implemented 
(no expansion) is probably the most practical approach.

An unconstrained expansion could easily overwhelm imagestack loading more 
frames than are strictly needed for the computation at hand.  Iteration over 
expanded groups of file should probably be handled by the user's script or 
application.

A slight adjustment to the loadframe documentation (not using a common wildcard 
character ) could make the existing functionality be a bit clearer to a new 
user.

Original comment by Terry.Th...@gmail.com on 11 Oct 2010 at 3:13

[GoogleCodeExporter]

This is a difference between command-line behavior on Windows and Unix-like 
shells. In Windows, programs are responsible for wildcard expansion, while on 
Unix, the shell is. So 'imagestack -loadframes foo*.jpg' will work just fine on 
Linux, Mac OS X, or in Cygwin on Windows, but won't work in the Windows shell.

Original comment by quantu...@gmail.com on 26 Oct 2010 at 8:25