jaPBe 1.4.4.25

[Dare2]

Hi GPI,

The problem is, that the line of the "End"-Procedure must not be after the line of the "Start"-Procedure.

Okay, understand. Thanks.

You can aktivate/deaktivate the auto-indent with F9 very fast.

Neat.

At the moment not.

No problem, it is pretty intuitive. Was just looking for the fine-tuning.

Thanks again.

[Chris]

Hi all

I don't know if it's a right place for this post, i'm sorry!

I've downloaded the new version of jaPBe, but I have a small problem.

With the previous versions, when I click a constant, (or a variable), in the panel to the right, the constant,(or variable), are written in the code, at the place of cursor.
This function don't work with the new version.

Why?. It's a bug ?

Chris

[GPI]

With the previous versions, when I click a constant, (or a variable), in the panel to the right, the constant,(or variable), are written in the code, at the place of cursor.
This function don't work with the new version.

Something internal in PB has changed. I will fix this.

[Chris]

Something internal in PB has changed. I will fix this.

Thank you GPI
(For your answer and for jaPBe too)

Chris

[blueznl]

gpi, just a suggestion for japbe: can compiler statements compilerif / comipiler case etc. be indented as well?

[GPI]

gpi, just a suggestion for japbe: can compiler statements compilerif / comipiler case etc. be indented as well?

no, because

Code: Select all

compilerif #debug
if a>10 and a<20
compilerelse
if a<20
compilerendif

[blueznl]

that's not much of a reason see what japbe turns that into:

Code: Select all

CompilerIf #debug 
If a>10 And a<20 
  CompilerElse 
  If a<20 
    CompilerEndIf 

so, it wouldn't matter much if the compiler statements would be indented, if you observe what happens above...