jaPBe 3.13.4 [IDE for PB 4 and PB 5]

[nicolaus]

How i can set 2 different source files in a split editor window?

You can't.

Can you add a option so that we can do this?

And if i split the editor window, the folding in the upper window works but not in the order one.

It's experimental and like it is said in the manual some scintilla features won't work in the 2nd window.

Ok thanks for this info.

[gnozal]

Can you add a option so that we can do this?

Probably not.
I had a lot of problems with SCI_SETDOCPOINTER, lots of unexpected callback bugs (compatibility problem with GPI's code ?). Maybe I didn't fully understand the scintilla docs. Anyway, I gave up on this as I don't need it.
But you know, jaPBe is open source, so you could try ...

[inc.]

There is a difference towards the IDE at the provided index of the linestart and lineend numbers when using the "PB_TOOL_Selection" Environment Variable.

If I do choose all lines for instance, the IDE Selection EnvVariable tells me it starts at line 1 which is correct, where the EnvVariable given by jaPBe tells me it starts at line 0. So jaPBe always does provide a linie number value which is less 1.

Can you duplicate that Gnozal?

Thanks a lot.
Inc.

[gnozal]

There is a difference towards the IDE at the provided index of the linestart and lineend numbers when using the "PB_TOOL_Selection" Environment Variable.
...
Can you duplicate that Gnozal?

Yes.
Note : for Scintilla, 1st line and 1st column are 0 (not 1).

[inc.]

There is a difference towards the IDE at the provided index of the linestart and lineend numbers when using the "PB_TOOL_Selection" Environment Variable.
...
Can you duplicate that Gnozal?

Yes.
Note : for Scintilla, 1st line and 1st column are 0 (not 1).

Yes I know that Scintilla Spec. and I dont want to stretch your efforts .... but our approach by enabling an IDE compilant EnvironmentVariable support is beeing more CrossEnvironmental.
So if we want the generated Plugin to be really CrossEnvironmental then imho we should be conform here to the IDE behaviour as well.

Otherwise the PlugIn-Programmer would have to implement a routine which checks the name of the plugin calling Environment and in case of 'jaPBe.exe' an incrementation of the line index must be kept in mind on further routines.

It would not be needed in case of handling "%SCI" (as maybe already some plugs have been build using it) but in the support of the IDE's "PB_TOOL_..." variables output we should be totally IDE conform.

Do you see my point.

[gnozal]

Do you see my point.

Sure

[gnozal]

Update build 692

Changes :
- added : custom indentation ; thanks 'Le Soldat Inconnu' (LSI) from french forum
- changed : PB_TOOL_SELECTION line / column start at 1
- changed : \Syntax folder no longer included in archive ; will be created by jaPBe if necessary
- updated : manual (separate download)

[nicolaus]

@gnozal

In the actual version of jaPBe i have a found a problem.
If you change in the project settings the XP Skinsupport to on, the Vista admin mode changes automaticly to off, but this is not right.

You can see and test it in the PB 4.20 beta 2 IDE. You can set the skin support and the adminmode of vista to on!

Please can you change this?

thanks,
Nico

[gnozal]

In the actual version of jaPBe i have a found a problem.
If you change in the project settings the XP Skinsupport to on, the Vista admin mode changes automaticly to off, but this is not right.

Did you try the option 'Request Admin mode on Vista' ?

[nicolaus]

In the actual version of jaPBe i have a found a problem.
If you change in the project settings the XP Skinsupport to on, the Vista admin mode changes automaticly to off, but this is not right.

Did you try the option 'Request Admin mode on Vista' ?

Yes

[gnozal]

In the actual version of jaPBe i have a found a problem.
If you change in the project settings the XP Skinsupport to on, the Vista admin mode changes automaticly to off, but this is not right.

Did you try the option 'Request Admin mode on Vista' ?

Yes

And ? Does it work ?
For your information :

Code: Select all

Option enabled     Manifest used (download jaPBe sources)
-----------------------------------------------------------
XPSkin             XP_Themes.manifest
Request Admin      Vista_RequireAdministrator.manifest
Request User       Vista_RequireUser.manifest

If it's wrong, please correct me (I don't have Vista).

[Wolfgang]

Last time I wrote:

I have one problem with japbe.
When I install new userlibraries or a new program version,
I often get an error message.
It says:
FATAL ERROR: ReadFile_() failed on InPipeRead
Possible causes:
- PBCompiler crash
- insufficient #PB410_PipeMaxLen

Now I changed the settings of #PB410_PipeMaxLen in the code to 800000.
After recompiling the source jePBe starts without error.

Therefore gnozal please increase #PB410_PipeMaxLen.
If this is not possible can you make a new option in jaPBe.prefs to adjust #PB410_PipeMaxLen by users themselves?

Thanks

[gnozal]

Now I changed the settings of #PB410_PipeMaxLen in the code to 800000.
After recompiling the source jePBe starts without error.

This is four times the default value ! You must have a lot of libraries installed.

Therefore gnozal please increase #PB410_PipeMaxLen.

Ok, will do.

[gnozal]

Update

Changes :
- changed : #PB410_PipeMaxLen = 800000 ; should be enough for everyone

[storck]

Hi!

I have tried to use jaBPe with PB 4.20 beta 2. It complains about not being able to load the compiler. Does this make any sense?

Regards,

Storck