Increased command line support

[GoogleCodeExporter]

It would be nice if the following arguments could be passed into gens via
commandline (not just a rom name):

-cfg [filename]  Would load a specific .cfg file (useful for having
multiple gens configurations without keeping copies of gens in separate
folders)

-playmovie [filename] Would play a specific gmv/gm2 when gens is loaded

-readonly [bool]  Set read only status

-loadstate [filename]

-pause [bool]  whether to start paused or unpaused 

Original issue reported on code.google.com by andres.d...@gmail.com on 15 Aug 2008 at 11:36

[GoogleCodeExporter]

I also request -capture [output_filename], which sets the rendermode to Normal, 
turns
off clean avi screen and disables all onscreen text apart from status messages.

Command line support should support more than 256 characters.

Original comment by farr...@bluetoaster.net on 15 Aug 2008 at 11:50

[GoogleCodeExporter]

I added -rom, -cfg, -play, -readwrite, -loadstate, -pause
-rom, -cfg, -play, -loadstate all require full paths (or must be in base 
directory?)
-pause and -readwrite will treat anything after them as a positive value (since 
there
is no logic in "-pause 0" or "-readwrite 0" since those are always going to be 
the
default values.

I am leaving open to discuss -capture.  Personally, I worry it is a bit 
not-feasible
since there are a lot more options needed to automatically set up avi recording 
(like
the codec).  Anyone else have any thoughts?

Original comment by andres.d...@gmail.com on 3 Nov 2008 at 5:05

[GoogleCodeExporter]

We could add a menu option that dumps out the contents of "AVICOMPRESSOPTIONS
m_options" and "WAVEFORMATEX m_soundFormat" from the AVIWrite class to a file, 
then
let the path to that file be an argument of -capture, so someone can set it up 
their
options once from the GUI and then reuse them later from the command line 
without
further prompting.

Original comment by nitsuja-@hotmail.com on 4 Nov 2008 at 9:32

[GoogleCodeExporter]

Hmm, I think I really like that idea.  Sounds easy to implement and quite 
useful.

Original comment by andres.d...@gmail.com on 4 Nov 2008 at 1:29

[GoogleCodeExporter]

I guess we should also have a -lua commandline that would load a lua script on 
startup.

Original comment by andres.d...@gmail.com on 22 Feb 2009 at 2:33

[GoogleCodeExporter]

Looking more at the idea of -lua, it looks really impractical for gens.  Lua 
scripts
are run from a dialog.  So we would need to open a dialog on startup then load 
a file
into that dialog externally, then run it externally.  That starts to sound a 
little icky.

So instead maybe the lua window should have an auto-load feature just like 
ramwatch.
 The gens window would open up the lua dialog, the dialog itself would auto-load the
script, all based on a bool flag stored in the cfg.  Any opinions?

Original comment by andres.d...@gmail.com on 25 Feb 2009 at 4:04

[GoogleCodeExporter]

-lua shouldn't be too hard, there's already a function that takes a script 
filename
and auto-opens a script dialog that starts running it. As for auto-load I prefer
having it hotkey based as it is now (all I have to do is hit Ctrl-L when I want 
to
load whatever set of Lua scripts I'm using, that way I can choose not to load 
them or
wait until a certain point before loading them).

Original comment by nitsuja-@hotmail.com on 25 Feb 2009 at 5:11

[GoogleCodeExporter]

I went ahead and added the -lua option.

Original comment by nitsuja-@hotmail.com on 25 Feb 2009 at 9:58