PureBasic Forums - English

oryaaaaa wrote:About Dont launch Debugger

Are you saying you can't use the debugger from jaPBe ?

oryaaaaa wrote:This code is created

Code: Select all

#jaPBe_CompilerVersion="4.01"
#jaPBe_IsDebuggerRunning=1
#jaPBe_IsExecute=0
#jaPBe_ExecuteBuild=1
#jaPBe_ExecuteType=0
#jaPBe_OnError=0
#jaPBe_SourcePath=""
#jaPBe_SourceFile=""
IncludePath "F:\Program Files\jaPBe\Include"
IncludePath ""
IncludeFile "F:\Program Files\PureBasic\Compilers\PB_EditorOutput2.pb"

Looks good to me !

Are you saying you can't use the debugger from jaPBe ?

Yes. Debugger can't start. Run/compile and CreateExecute is normal.

Add Problems

My enviroment
Multi Monitor 1:(0,0) Video,Game 2:(-1280,0) PureBasic/Firefox
nVIDIA nView Manager enable

Autocomplete display becomes bihind full screen video output.
No look autocomplete.

Visual Designer Starter.pb is normal and may be a bug of PB3.94.
It vrifies later.

Sorry, I really don't know what could be the problem ...

Just some Syntax-highlighting problems:
- If (Not a)
"Not" is not highlighted as a keyword, Not is always a keyword, I don't think
you have to look at the context (if there is a space between ( and Not, it
works)?

- The use of the operator # within macros is wrongly highlighted, perhaps
you could just disable constants highlighting within macros?


- I'm not sure why, but I'm not able to change the debugger settings...
If I press OK and reopen the preferences, everything is like it was, nothing
changed.


And VERY rarely I loose all my preferences and have to set up everything
again :roll: (just started jaPBe and everything was set to standard)

remi_meier wrote:- If (Not a) "Not" is not highlighted as a keyword, Not is always a keyword, I don't think you have to look at the context (if there is a space between ( and Not, it works)?

Not is handled like any other basic keyword, but you are right, there was a problem. Should be fixed in jaPBe 3.6.12.

remi_meier wrote:- The use of the operator # within macros is wrongly highlighted, perhaps you could just disable constants highlighting within macros?

The current syntax coloring routine does not know if a line is in a macro block or not. It's currently only possible if you scan the whole source (like when you load a file).

remi_meier wrote:- I'm not sure why, but I'm not able to change the debugger settings...
If I press OK and reopen the preferences, everything is like it was, nothing changed.

You are right ! The code was broken since a few versions. Should be fixed in jaPBe 3.6.12.

remi_meier wrote:And VERY rarely I loose all my preferences and have to set up everything again :roll: (just started jaPBe and everything was set to standard)

I never had this one since I use jaPBe . Was jaPBe.pref absent or zero file ?

Update 3.6.12

Changes :
- 2 bugs fixed (see previous post)
- 2 new styles (dobro.txt and flype.txt)

The current syntax coloring routine does not know if a line is in a macro block or not. It's currently only possible if you scan the whole source (like when you load a file).

Ok, I will live with it

I never had this one this I use jaPBe . Was jaPBe.pref absent or zero file ?

Sorry, I didn't pay enough attention, I will next time it happens. If I
remember correctly, the first time it happened I looked what the content
of jaPBe.pref was, I think all just was reset to standards (right after
starting jaPBe).

Thx for the fixes!

New jaPBe BETA

- added support for custom keywords / folding
It can be enabled in the new 'Custom keywords' tab in Preferences.

I didn't want to change too much jaPBe code, so there are two lists :
- one for syntax coloring : file jaPBe_Keywords.pref
- one for folding : file jaPBe_FoldingKeywords.pref
Some of the 'folding' parameters are not documented, so just keep the default values unless you know what you are doing.

Happy testing !

Download it here : http://people.freenet.de/gnozal/jaPBeFo ... FOLDING.7z

Great!

Big thx.

But please documente the folding parameters.

mknjc wrote:But please documente the folding parameters.

It's very difficult to explain, and you don't really need them to enable folding. It's mostly for compatibility with the existing jaPBe code.
If you really want to know more, have a look at Editor-Core.pbi in the sources and search for : Markit, NextType, Struc$ and Ok.
The beta sources will be available when it's no more a beta.

In the mean time, please post any bugs related to this beta.

jaPBe BETA updated

- added 'Exclude comments and strings' option in Find dialog [language file entry 564]

Download it here : http://people.freenet.de/gnozal/jaPBeFo ... FOLDING.7z

Visual Designer

Test in OtherPCs. connect USB-HDD F drives.

Result: no problem

This trouble is My PC only? I will dive windows

jaPBe 3.6.12 build 600

Changes :
- added 'Exclude comments and strings' option in Find dialog
- added custom keywords and folding
- new style : Flaith.txt

Note : unlike the beta, the custom keyword preference files are stored in %jaPBe%\Syntax. They are named jaPBe_FoldingKeywords.pref.Original and jaPBe_Keywords.pref.Original, so your modified preference files are not overwritten. If there are no user modified files, jaBPe will copy jaPBe_FoldingKeywords.pref.Original to jaPBe_FoldingKeywords.pref and jaPBe_Keywords.pref.Original to jaPBe_Keywords.pref the first time you activate the custom keywords.

My trouble solved (by update 4.02)
*Debugger, VD

I am new to jaPBe and PureForm, so forgive me if my questions are newb-like.

Both programs are fantastic, but I feel a bit lost on a couple of features:

1) Can someone explain jaPBe projects to me?
a) Do you reopen a project by opening the .pbfl file?
b) Are there other advantages to using projects beyond (a)

2) What is the best way to use the PureForm plugin to maintain forms within jaPBe projects?
a) Should I create a separate .pbf file, use "Save as code" to create a separate .pb file and add it to the jaPBe project, or use the code windows "Copy code to jaPBe"?
b) If I later modify the window/gadget code, do I always need to use "Translate from source" to get the changes recognized in PureForm, or is there some way to have PureForm rescan the code automatically?

What I am really trying to learn is the most efficient way to use projects and PureForm together.