Hi
for what reason is the command window? Compared with the old debugger I
expected that I can write there commands and get the answers in the command
output window. But if I write there maybe a var name (like Im used to do in
the old debugger) I get only the answer "unknown function"
Is the command window not yet finished? The help to the command output
window leads to this thought.

Is there somewhere a list of all unfinished features that makes it
unnecessary to ask for all unexpected behavior of VX?
Thank you

Klemens

"Klemens Lichter" <csl@lichter.de> wrote in message
news:YQ4XM4rzDHA.3332@S15147418...
> for what reason is the command window? Compared with the old
> debugger I expected that I can write there commands and get the
> answers in the command output window. But if I write there maybe
> a var name (like Im used to do in the old debugger) I get only the
> answer "unknown function" Is the command window not yet finished?
> The help to the command output window leads to this thought.

Klemens,

the command window goes beyond the scope of just the
debugger. It provides an extensible command interface that can
parse and execute arbitrary commands. Commands recognised
by the Command Window usually use a prefix that allow the
command processor to distinguish between different "name spaces"
and to associate a command with a package that can execute it. In
the case of the debugger, commands are prefixed with a ".".

To inspect a variable, for instance, use
  .<myvariablename> or
  .<myvariablename> := <expr> etc.

If you omit the "." prefix, the command is executed in the
IDE's boxed runtime. Just try entering
  time()  or
  xbpcrt():new():create()

Erm ..., better forget the last one .

By the way, another way to inspect variables and such
while debugging is either to use the debugger tooltip
feature, or to press Ctrl+F7 to open the Expression
Inspector.

Please note that the command interface is still under
construction. That's why the docs on it are a bit sparse
.

Hope that helps,
  Till

--
---------------------------------------------------
ARD - Alaska Research & Development

Web:       http://www.alaska-research.com
Investors: http://www.alaska-research.com/tifund
E-Mail:    mailto:till.warweg@alaska-research.com
Contact:   mailto:info@alaska-research.com
---------------------------------------------------

Thank you Till,
its OK.

Klemens

"Till Warweg" <till.warweg@alaska-research.com> schrieb im Newsbeitrag
news:6lqvVKtzDHA.1976@S15147418...
> "Klemens Lichter" <csl@lichter.de> wrote in message
> news:YQ4XM4rzDHA.3332@S15147418...
> > for what reason is the command window? Compared with the old
> > debugger I expected that I can write there commands and get the
> > answers in the command output window. But if I write there maybe
> > a var name (like Im used to do in the old debugger) I get only the
> > answer "unknown function" Is the command window not yet finished?
> > The help to the command output window leads to this thought.
>
> Klemens,
>
> the command window goes beyond the scope of just the
> debugger. It provides an extensible command interface that can
> parse and execute arbitrary commands. Commands recognised
> by the Command Window usually use a prefix that allow the
> command processor to distinguish between different "name spaces"
> and to associate a command with a package that can execute it. In
> the case of the debugger, commands are prefixed with a ".".
>
> To inspect a variable, for instance, use
>   .<myvariablename> or
>   .<myvariablename> := <expr> etc.
>
> If you omit the "." prefix, the command is executed in the
> IDE's boxed runtime. Just try entering
>   time()  or
>   xbpcrt():new():create()
>
> Erm ..., better forget the last one .
>
> By the way, another way to inspect variables and such
> while debugging is either to use the debugger tooltip
> feature, or to press Ctrl+F7 to open the Expression
> Inspector.
>
> Please note that the command interface is still under
> construction. That's why the docs on it are a bit sparse
> .
>
> Hope that helps,
>   Till
>
> --
> ---------------------------------------------------
> ARD - Alaska Research & Development
>
> Web:       http://www.alaska-research.com
> Investors: http://www.alaska-research.com/tifund
> E-Mail:    mailto:till.warweg@alaska-research.com
> Contact:   mailto:info@alaska-research.com
> ---------------------------------------------------
>
>
>

I'm using ctrl-F7 (Evaluate expression) to do this. It also is then easy 
to add to the watch if needed.

Jim


Klemens Lichter wrote:
> Hi
> for what reason is the command window? Compared with the old debugger I
> expected that I can write there commands and get the answers in the command
> output window. But if I write there maybe a var name (like I´m used to do in
> the old debugger) I get only the answer "unknown function"
> Is the command window not yet finished? The help to the command output
> window leads to this thought.
> 
> Is there somewhere a list of all unfinished features that makes it
> unnecessary to ask for all unexpected behavior of VX?
> Thank you
> 
> Klemens
> 
>