Re: [Pythoncard-users] Estimated release date for new version of PythonCard

[Brian M. <mrb...@gm...>]

I'm not going to be set up for CVS soon enough. My input is
based on the current release of PythonCard for Windows.
I want to check on the Property Editor run options problem.
These are collected as a string from the "Other args" text field
in the "Run Options" window launched from the Property Editor.
Things go well until all args are copied into self.cmdLineArgs in
getCommandLineArgs() in resourceEditor.py. This method has
no self.cmdLineArgs['otherargs'] so the other args string never
makes it into the args variable of runScript().

Actually, I'm not sure if I want them in the args variable, anyway.
If I'm using the optparse module or the clever recipe for parsing
a docstring to validate command line options
http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/278844
then the additional PythonCard options mess up my valid
command line options. I think in 99% of cases these PythonCard
options are only used by a developer, not an end user, who is running
a program with only the options which I am ready to handle with
my code.

Maybe I would be better off if the Property Editor run options window
let me save all options as one environment variable. Or anything that
would leave the command line options as I intended while getting
the "run options" information to the PythonCard initialization.

Is this too much to ask? Especially as no one else has complained
about this. I just really like documenting and validating my command
line args and the Property Editor arg technique makes it difficult.

Any ideas?

On 11/10/05, Phil Edwards <ph...@li...> wrote:
>
> On Thu, 2005-11-10 at 23:14 +1100, Andy Todd wrote:
> > > If people want to post specific issues with the current release,
>
>
>