jaPBe 3.13.4 [IDE for PB 4 and PB 5]

[Mistrel]

A global default for new projects would make more sense. An override might be confusing to the user when JaPBe still compiles to the local directory because of the source option.

[Mistrel]

I use these variables for some of my tools with the PureBasic IDE. It would be nice if JaPBe supported these so that they could be compatible.

[gnozal]

I use these variables for some of my tools with the PureBasic IDE. It would be nice if JaPBe supported these so that they could be compatible.

jaPBe supports the following tool variables (from manual) :

Code: Select all

%PATH
 The path of the current file. 
%FILE
 The file name inclusive the path of the current file. 
%EXECUTABLE
 This will be replaced by the name of the executable that was created in with the last "Create Executable" [F7].
 For the "After Compile/Run" trigger, this will be replaced with the name of the temporary executable file created by the compiler [F5]/[F6].
 Note : this parameter is only available for PB versions >= 4.10. 
%TEMPFILE
 The current source code is saved in a temporary file, and the filename is inserted here. You may modify or delete the file at will. 
%COMPILEFILE
 This is replaced with the temporary file that is sent to the compiler for compilation. By modifying this file, you can actually change what will be compiled 
%CURSOR
 This will be replaced by the current cursor position, in the form of LINExCOLUMN. 
%WORD
 Contains the word currently under the cursor. 
%JAPBE
 This will be replaced by the jaPBe main window handle. 
%SCI
 This will be replaced by the Scintilla window handle.

If it isn't enough, jaPBe also supports the PB_TOOL_* environment variables (see PB help for more details).

[eriansa]

a very big "thank you" to you sir!

[Kukulkan]

Hi Mistrel,

A global default for new projects would make more sense.

This is exactly what I meant with "global definition".

A project-option with a global set default value.

100% ACK.

Kukulkan

[Kukulkan]

Hi gnozal,

added 'Create temp EXE in source dir' in project options

Not tested yet, but thank you very much!

Kukulkan

[dobro]

Hi gnozal,

added 'Create temp EXE in source dir' in project options

Not tested yet, but thank you very much!

Kukulkan

ouaip pareil !! ( yes ! +1 )

[Dummy]

In the latest version JaPBe hangs for several seconds while starting up. This slows down the general startup process of JaPBe what is really annoying when starting and closing JaPBe often as I do.
Please fix it (JaPBe Version 3.8.5.702)

[gnozal]

In the latest version JaPBe hangs for several seconds while starting up. This slows down the general startup process of JaPBe what is really annoying when starting and closing JaPBe often as I do.
Please fix it (JaPBe Version 3.8.5.702)

1. It noticed a delay with PB4.20 too if 'Load constants from residents' is enabled. If it is the case, disable it. I don't know why, no change in the code.
2. No other delay here. The PBCompiler pipe communication code in jaPBe hasn't changed either. Maybe something changed on compiler side.
3. The only change in startup code between build 701 and 702 is the PB version information in the title bar (displayed when PBCompiler is ready).
4. Btw, why do you need 'starting and closing JaPBe often' ?

[Dummy]

In the latest version JaPBe hangs for several seconds while starting up. This slows down the general startup process of JaPBe what is really annoying when starting and closing JaPBe often as I do.
Please fix it (JaPBe Version 3.8.5.702)

1. It noticed a delay with PB4.20 too if 'Load constants from residents' is enabled. If it is the case, disable it. I don't know why, no change in the code.
2. No other delay here. The PBCompiler pipe communication code in jaPBe hasn't changed either. Maybe something changed on compiler side.
3. The only change in startup code between build 701 and 702 is the PB version information in the title bar (displayed when PBCompiler is ready).
4. Btw, why do you need 'starting and closing JaPBe often' ?

1. I did notice that an hour after that post, too. But disabbling is not a real solution as I use the autocompletition feature very often for constants.
2. Same here it's just the "loading residents..." step
3. I don't update my JaPBe very often and I don't remember what the last version before was.
4. It's some kind of a bad habbit that mainly comes from the fact that I use a special utility to build my projects and close the editor before compiling to enshure that the running compiler of JaPBe doesn't disturb the compilation process.

[gnozal]

Update

Changes :
- fixed delay when starting jaPBe with PB4.20 and 'Load constants from residents' is enabled

[Dummy]

Update

Changes :
- fixed delay when starting jaPBe with PB4.20 and 'Load constants from residents' is enabled

Thanks for fixing it

[eriansa]

Latest update (with "Create temp exe in source directory) contains an annoyance : the editor (when using multi source files) allways reverts after compilation to the main file.

[gnozal]

Latest update (with "Create temp exe in source directory) contains an annoyance : the editor (when using multi source files) allways reverts after compilation to the main file.

Should be fixed.
Download updated.

[ebs]

I believe I have found a bug when specifying the program command line in jaPBe.
Here is a simple program to demonstrate the bug:

Code: Select all

Artist.s = ProgramParameter()
Album.s = ProgramParameter()
Title.s = ProgramParameter()

MessageRequester(#Null$, Artist + #CRLF$ + Album + #CRLF$ + Title) 

In jaPBe, I set the command line to:

Code: Select all

"Artist Name" "Album Name" "Song Name"

and run the program. The message box shows:

Code: Select all

Artist

Name"

which is not correct.

Running the compiled program with the same command line,
or running it in the standard PB editor produces the expected results:

Code: Select all

Artist Name
Album Name
Song Name

I am running jaPBe 3.7.11.677 and PB 4.20. Can someone confirm this?

Regards,
Eric