12 replies to this topic

[pscEx]

At a different place I answered this:

I built a snippet following your description.

[process]

	 Set,%result%,"Does not work"

	 If,5,EQUAL,5,Set %Result%,"Works!"

	 Echo,%Result%

See missing comma behind 'Set'

In 072 the result has been the same like as if there had been a comma, in 076 it is not.

Is 076 now "Bad programmed"?

I really do not think so.

In 072 the uncorrect syntax has been understood correctly by 'good luck'. There is no code to solve such errors.
I do not know what happens with different user input mistakes.

And 076 shows you that there is something wrong.

Peter

Because I think that this question is very important, I repeat here.

I hope on your agreement that WinBuilder never tries to 'fix' user mistakes, but ALLWAYS gives an error.

Peter

[allanf]

At a different place I answered this:

Because I think that this question is very important, I repeat here.

I hope on your agreement that WinBuilder never tries to 'fix' user mistakes, but ALLWAYS gives an error.

Peter

The answer is definitely 'NO'!

... ... I mean 'YES'!

Sorry!? What was the question? ... ...

... The new way is better! ... ...

Regards

[Lancelot]

WinBuilder never tries to 'fix' user mistakes, but ALLWAYS gives an error.

%100 agree. (i guess no need to write the good reasons in mind )

[pscEx]

I made a small change to WinBuilder, two additional options:

Lines starting with // or ## are treated as comment.
Other non-command lines are shown as warnings.

A first test with LiveXP recommended brought an interesting result:

@Galapo: Something to do for you!

@Medevil: Your WB072 will make you happy and neither process nor message these lines!

Peter

[MedEvil]

Is there a way to get my hand on this verbose version?

[pscEx]

Is there a way to get my hand on this verbose version?

I'm not authorized to publish it (you remember the troubles we have had with 075 beta nightlies, because nobody took care on any rules).

Post your complete test project anywhere and / or give the link. I'll build and post the log.

Peter

[allanf]

Lines starting with // or ## are treated as comment.
Other non-command lines are shown as warnings.

So:

#--- Hello ---#

will show as a warning?

##--- Hello ---##

will show as a comment?

###--- Hello ---###

will also show as a comment?

and:

Hello

will show as a warning (assuming no API for 'Hello')?

Is that correct?

Where do the comments show in the log? In the beginning (as links), or throughout?

It sounds like a very good idea!

Regards

[Galapo]

A first test with LiveXP recommended brought an interesting result:

@Galapo: Something to do for you!

Thanks, Peter. WB can now find bugs!

Regards,
Galapo.

[pscEx]

So:

#--- Hello ---#

will show as a warning?

##--- Hello ---##

will show as a comment?

###--- Hello ---###

will also show as a comment?

and:

Hello

will show as a warning (assuming no API for 'Hello')?

Is that correct?

Where do the comments show in the log? In the beginning (as links), or throughout?

It sounds like a very good idea!

Regards

All of your assumptions are correct.

The comments will appear in place.
The Unresolved as links and in place.

Peter

[Lancelot]

Lines starting with // or ## are treated as comment.
Other non-command lines are shown as warnings.

I like that .

Never wrote before but when making gui design sometimes i disable an option from interface but i want to keep it available for future purposes too, because wb dont support // or ##, at [Interface] section so far i open a new section [Interfacesave] and move lines to there.

can we have these work // or ## for [Interface] section, or another thing?

[pscEx]

I like that .

Never wrote before but when making gui design sometimes i disable an option from interface but i want to keep it available for future purposes too, because wb dont support // or ##, at [Interface] section so far i open a new section [Interfacesave] and move lines to there.

can we have these work // or ## for [Interface] section, or another thing?

Not yet. Implementation seems to be difficult, because the complete interface is rewritten after changes.
And then the comments are 'unknown'.

Peter

[pedrole15]

I made a small change to WinBuilder, two additional options:
Lines starting with // or ## are treated as comment.
Other non-command lines are shown as warnings.

Ok, so they become the official 'comment' command
In VistaPE , I remember that NightMan use sometime only one character '#' as comment ( just for info)

Pedro

[allanf]

Ok, so they become the official 'comment' command
In VistaPE , I remember that NightMan use sometime only one character '#' as comment ( just for info)

Pedro

I think psc is aware of that. Possibly it's the reason for introducing it. Who knows? It's all very secretive.

Regards