PureBasic Forums - English

Hi gnozal
Can you add a shortcut Ctrl-[ and Ctrl-]. Most editors have this and if you press this while cursor is in }, cursor will go to its partner {.

If you will press the shortcut (Ctrl-[) while example in keyword EndIf, the cursor will go to partner If.
Iif EndProcedure, cursor will go to Procedure.
If ) it will go to the highlighted (.

Benefit:
Easier to go to the Open/Close keyword if the code is very long without scrolling up or down searching.
Or possibly to avoid something like this: here

PS: If only the codebase is v4.x I will play on it and try to add that before asking.

Seems a good idea for me - in general...
The problem i see is the Key [.
On somekeyboards you have to press ALT + (Whatsoever) to get this char.
With Crtl + Alt + 8 (on my keyboard) its not so comfortable...Maybe a bit an "international" key to choose..

Visual Studio uses Ctrl-[ and Ctrl-]
And also crimson editor and others.

Maybe a feature to customize our own shortcut?

I didnt use Visual Sudio by the way... and I never will

A customizeable shortcut would be fine for me

Update

Changes :
- this release should fix jaPBe sometimes freezing while processing successive undos (CTRL+Z/CTRL+Z/CTRL+Z/....)

gnozal wrote:Update

Changes :
- this release should fix jaPBe sometimes freezing while processing successive undos (CTRL+Z/CTRL+Z/CTRL+Z/....)

Oh yeah That still arrived to me yesterday.

Update

Changes :
- Tools setup : fixed %TEMPFILE
- Tools setup : added %COMPILEFILE

japbe .. the only way i role

http://www.liquidbuzz.com/images/pb/desktop1.jpg

- np

Any chance to add the following (ripped from 4.10 windows notes)
Into the project options window? It currently breaks getting the actual exe path right now

X wrote:Any chance to add the following (ripped from 4.10 windows notes)

Code: Select all

- the temporary exe can be created in the source directory 

Into the project options window?

When using PB4.10, jaPBe uses the windows temp directory to create the temporary exe (when using PB4.0x, it's created in \Compilers).

X wrote: It currently breaks getting the actual exe path right now

What do you mean with 'getting the actual exe path' ?
Look in %TEMP% instead of \Compilers.

Like the following directory structure

/client
/client/bin-src
/client/data

The source code is in the /client/bin-src directory, thus would be the exe when compiled. The pref file would be in the /client/data directory. Normally, I would grab the exe's location, and do something like
How would this be possible now that the exe is compiled to the %temp% directory without using hard coded paths? ala, c:\<blah>\<blah>\client\data\config.ini. Since not everybody's machine is the same

(edit): There seems to be a #PB_Compiler_Source flag (or some such) some where that might be useful.

Yes, you have to use #PB_Compiler_File.

Update

Changes :
- jaPBe now copies the original source file to a temp file before compiling. %COMPILEFILE holds the name of this temp file.
- %COMPILEFILE can be modified before compiling by a plugin triggered by events 'Before Compile/Run' or 'Before Create EXE'
- so jaPBe should be more compatible with some PB IDE plugins.

I still can't get analyser working

I put the path to analyser.exe in the tool menu and when I click the menu I never see the analyser window... the one that says on or off....

I've tried the analyser.exe in both the pb dir and the jaPBe dir and no difference.

It works perfectly in the PB IDE.

Has anybody managed this ?

dontmailme wrote:I still can't get analyser working

I put the path to analyser.exe in the tool menu and when I click the menu I never see the analyser window... the one that says on or off....

I've tried the analyser.exe in both the pb dir and the jaPBe dir and no difference.

It works perfectly in the PB IDE.

Has anybody managed this ?

I don't know exactly what it is supposed to do, but I get this (after F5 'Compile/Run') :
1. MessageBox "Started!"
2. My app starts
3. I quit my app
4. MessageBox "Finished!"
5. Analyser window with a ListIconView 'LineNb/TotalTime/%Time...'

I had to activate Analyser the first time : double-click on Analyser.exe (--> Analyze = 1 in analyzer.ini)

In tools : Arguments = "%COMPILEFILE" ; Trigger = "Before Compile/Run"

If this is the expected behaviour, I suggest the following :
- create one tool named "Analyzer", Arguments = "%COMPILEFILE", Trigger = "Before Compile/Run" and hide it (so you don't see it in the menu).
- create another tool named "Analyzer On/Off", Arguments = <Empty> , to enable / disable the analyser when you click on it in the menu.