ok,
that is what i want to understand.
so i can do
txtResult.Text &= Str(hExpression.Value) & gb.NewLine
and works fine!
Thanks Tobias and Benoit.
On Sun, 2011-09-25 at 01:31 +0200, Benoît Minisini wrote:
> > yes PRINT gives TRUE.
> >
> > why that?
> >
>
> Because Print uses Str$() and no
> yes PRINT gives TRUE.
>
> why that?
>
Because Print uses Str$() and not CStr() to convert its arguments to something
printable.
--
Benoît Minisini
--
All of the data generated in your IT infrastructure is seriously
> yes PRINT gives TRUE.
>
> why that?
i thought, i explained it already ;)
obtaining hExpression.Value and calling Eval() do the same, you will get
the same result.
Print prints an expression, this is not limited to a string, even not
limited to a variant, because you can print objects, too, but
yes PRINT gives TRUE.
why that?
On Sat, 2011-09-24 at 21:46 +0200, tobias wrote:
> On 24.09.2011 21:44, Demosthenes Koptsis wrote:
> > txtResult.Text&= CStr(hExpression.Value)
> >
> > gives the same result with
> >
> > txtResult.Text&= hExpression.Value
> >
> > which is "T"
> >
> > i think gamba
On 24.09.2011 21:44, Demosthenes Koptsis wrote:
> txtResult.Text&= CStr(hExpression.Value)
>
> gives the same result with
>
> txtResult.Text&= hExpression.Value
>
> which is "T"
>
> i think gambas3 make in the background the convertion (i think...) and
> CStr may be is useless.
>
of course, you ass
txtResult.Text &= CStr(hExpression.Value)
gives the same result with
txtResult.Text &= hExpression.Value
which is "T"
i think gambas3 make in the background the convertion (i think...) and
CStr may be is useless.
On Sat, 2011-09-24 at 19:29 +0200, tobias wrote:
> On 24.09.2011 18:50, Demos
On 24.09.2011 18:50, Demosthenes Koptsis wrote:
> so True = T and False = Null for
> txtResult.Text&= CStr(hExpression.Value)& gb.NewLine
>
> that i also get.
>
>
> I just wonder if this is correct.
> i expected the same functionality with Eval().
>
>
>
i suppose, it *has* the same functionality
so True = T and False = Null for
txtResult.Text&= CStr(hExpression.Value)& gb.NewLine
that i also get.
I just wonder if this is correct.
i expected the same functionality with Eval().
On Sat, 2011-09-24 at 17:44 +0200, tobias wrote:
> On 24.09.2011 17:12, Demosthenes Koptsis wrote:
> > i h
On 24.09.2011 17:12, Demosthenes Koptsis wrote:
> i have the next lines to make an gb.eval example
>
>
> Public Sub btnEval_Click()
>
>Dim hExpression As Expression
>hExpression = New Expression
>
>hExpression.Text = txtEval.Text
>txtResult.Text&= CS
i have the next lines to make an gb.eval example
Public Sub btnEval_Click()
Dim hExpression As Expression
hExpression = New Expression
hExpression.Text = txtEval.Text
txtResult.Text &= CStr(hExpression.Value) & gb.NewLine
Print Eval(txtEval.Text)
10 matches
Mail list logo