Hi,

I have imported my project and built it. So far so good.

I specify a different directory as a runtime parameter, then click on run.

It doesn't seem to work. If I go back to the parameters, what I typed has
disappeared but is still in the pull down.



Mike

Hi Mike,

You are right. I could reproduce the behaviour you described.
Runparameters should be stored and maintained in the project file
in the same manor like breakpoints, watchpoints and a list of
current open files.
And this is the place where the workaround is to be placed:

Open the Project.xpj file before it is loaded with VisualXbase++.

Add a line in the target section:

[PROJECT]
   Version = 2.0
   Project.xpj

[Project.xpj]
   test.exe

[test.exe]
   Compile  = xpp

    ...

   RC_FLAGS = /v
   RUNPARAMETER = param1 param2 ... param3    <- this is the
    $START-AUTODEPEND                          important line


   ...

Then open the project with VX. When activating the target test.exe
with double click on the target.exe node of the project manager,
the Runparameter Dialog displays param1 param2 ... param3

When debugging the executable you can see that these parameters
have been passed to the procedure main() (check with PCount() and
PValue() ).

It is not clear why this feature is broken and the bug has past
our QA tests. We have to investigate in this.



Best Regards and Happy X-Mas


Andreas Herdt


//////////////////////////////////////////////////////////////////

 Alaska Research & Development
 Homepage: www.alaska-research.com
 Newsgroup: nntp://news.alaska-Software.net

//////////////////////////////////////////////////////////////////

Mike Grace wrote:

> Hi,
> 
> I have imported my project and built it. So far so good.
> 
> I specify a different directory as a runtime parameter, then click on run.
> 
> It doesn't seem to work. If I go back to the parameters, what I typed has
> disappeared but is still in the pull down.
> 
> 
> 
> Mike

Thanks Andreas

I'll put that in.

Regards


Mike

"Andreas Herdt" <andreas.herdt@alaska-research.com> wrote in message
news:zMM$xVhyDHA.2908@S15147418...
> Hi Mike,
>
> You are right. I could reproduce the behaviour you described.
> Runparameters should be stored and maintained in the project file
> in the same manor like breakpoints, watchpoints and a list of
> current open files.
> And this is the place where the workaround is to be placed:
>
> Open the Project.xpj file before it is loaded with VisualXbase++.
>
> Add a line in the target section:
>
> [PROJECT]
>    Version = 2.0
>    Project.xpj
>
> [Project.xpj]
>    test.exe
>
> [test.exe]
>    Compile  = xpp
>
>     ...
>
>    RC_FLAGS = /v
>    RUNPARAMETER = param1 param2 ... param3    <- this is the
>     $START-AUTODEPEND                          important line
>
>
>    ...
>
> Then open the project with VX. When activating the target test.exe
> with double click on the target.exe node of the project manager,
> the Runparameter Dialog displays param1 param2 ... param3
>
> When debugging the executable you can see that these parameters
> have been passed to the procedure main() (check with PCount() and
> PValue() ).
>
> It is not clear why this feature is broken and the bug has past
> our QA tests. We have to investigate in this.
>
>
>
> Best Regards and Happy X-Mas
>
>
> Andreas Herdt
>
>
> //////////////////////////////////////////////////////////////////
> 
>  Alaska Research & Development
>  Homepage: www.alaska-research.com
>  Newsgroup: nntp://news.alaska-Software.net
> 
> //////////////////////////////////////////////////////////////////
>
> Mike Grace wrote:
>
> > Hi,
> >
> > I have imported my project and built it. So far so good.
> >
> > I specify a different directory as a runtime parameter, then click on
run.
> >
> > It doesn't seem to work. If I go back to the parameters, what I typed
has
> > disappeared but is still in the pull down.
> >
> >
> >
> > Mike
>