jaPBe 1.4.3.27
jaPBe 1.4.3.27
Here is the newest update of "just another PureBasic editor".
(downloadlink in the signature)
* Compileable only with PB3.89!
* Better GoTo-Dialog
* Add Interfaces to the structure-viewer
* jaPBe could crash at end and destroy the japbe.pref
* Select a text to set the start-Value of the "Pick Color"-Tool (a complete selected RGB($10,$20,$50) will work)
* Alt open the menu again
* Repair "Open Backup"
* When the first line of a Backup-File is ";info:" this info will be display in OpenBackup
* ToolTip of the FilePanel show the Full File Name
* Small changes in Config Tools
(Add-Button removed. You must select now the insert-position; bar insert on actual position)
* CompilerFlag could be ignored on Compile/Run/Debug
* Again a little bug in the find-window
* Remove left-click-on-file-panel-open-popupmenu (some problems detected)
* Extends-Style-Bug
* Resources overwork. Reshacker is not needed anymore
* Compile .RC-Files will create .obj (and not .res)
* Default Resource-Files is now .obj (and not .res)
* Better Methode to get the output of GoRC (on win9x-System about 10x faster...)
* New "Compiling" indicator in the statusbar
MessageRequester
* Add a # for IdAbort.
CodeTemplate
* Change WindowEvent() to WaitWindowEvent()
(I upload at the moment, so look at the file-format)
(downloadlink in the signature)
* Compileable only with PB3.89!
* Better GoTo-Dialog
* Add Interfaces to the structure-viewer
* jaPBe could crash at end and destroy the japbe.pref
* Select a text to set the start-Value of the "Pick Color"-Tool (a complete selected RGB($10,$20,$50) will work)
* Alt open the menu again
* Repair "Open Backup"
* When the first line of a Backup-File is ";info:" this info will be display in OpenBackup
* ToolTip of the FilePanel show the Full File Name
* Small changes in Config Tools
(Add-Button removed. You must select now the insert-position; bar insert on actual position)
* CompilerFlag could be ignored on Compile/Run/Debug
* Again a little bug in the find-window
* Remove left-click-on-file-panel-open-popupmenu (some problems detected)
* Extends-Style-Bug
* Resources overwork. Reshacker is not needed anymore
* Compile .RC-Files will create .obj (and not .res)
* Default Resource-Files is now .obj (and not .res)
* Better Methode to get the output of GoRC (on win9x-System about 10x faster...)
* New "Compiling" indicator in the statusbar
MessageRequester
* Add a # for IdAbort.
CodeTemplate
* Change WindowEvent() to WaitWindowEvent()
(I upload at the moment, so look at the file-format)
Thanks GPI. Is it useable with 3.81? Any English help yet? Eg, Cutter - only recently discovered what it does, help would of, well, helped me use it a lot sooner
Also noticed that Cutter can include "include" files twice (or more). I need to check further but it may be due to paths. I'll try to explain best I can...
Main file (directory "C:\projects\main.main.pb", includes...
> util1.pb (directory "..\util1\util1.pb"), which includes...
>> genutils.pb (directory "..\gen\genutils.pb")
> util2.pb (directory "..\util2\util2.pb"), which includes...
>> genutils.pb (directory "..\gen\genutils.pb")
...and genutils.pb gets included twice
Clear as mud? 

Main file (directory "C:\projects\main.main.pb", includes...
> util1.pb (directory "..\util1\util1.pb"), which includes...
>> genutils.pb (directory "..\gen\genutils.pb")
> util2.pb (directory "..\util2\util2.pb"), which includes...
>> genutils.pb (directory "..\gen\genutils.pb")
...and genutils.pb gets included twice


Thanks for this,
Just 2 questions for next versions (sorry if this has already been asked or written somewhere):
- could it be possible that we can settle a special color (as for Asm) for debugger purposes (more readable and debugger is very useful for new Pb's as I am - well I speak for me of course);
- could it be possible that we can settle a special color to distinguish PB's key words (there is a possibility for Basic terms) from functions ans procs create by the coder ?
Excpeted if I missed these points, it is not possible to do those things.
Anyhow thanks for JaPBe,
Fiwip
Just 2 questions for next versions (sorry if this has already been asked or written somewhere):
- could it be possible that we can settle a special color (as for Asm) for debugger purposes (more readable and debugger is very useful for new Pb's as I am - well I speak for me of course);
- could it be possible that we can settle a special color to distinguish PB's key words (there is a possibility for Basic terms) from functions ans procs create by the coder ?
Excpeted if I missed these points, it is not possible to do those things.
Anyhow thanks for JaPBe,
Fiwip
?! It should be fixed. Otherwise: Please explain exact, what's wrong.Shannara wrote:Nice updateAny chance to fix the Extends bug?
@dmoc:
It should work with 3.81 (i only make a quick test; but should work). The structure viewer is then unable to show interfaces.
I will look at cutter.
@fiwip
Intresting suggestions. Maybe.
I forgot to update the language files. I upload this file in a zip.
Something about "find back"
jaPBe stores now the start point of each search. With F4 you can jump back to the root of your search. jaPBe can store about 100 "jump backs". Also "goto line" and "find declaration" store there beginning position.
"Find back" take care about deleted lines and closed files.
Normaly it is usefull, when every "find next" is stored in this memory. So it can be set in the preferences, that only new searchs are stored. This is the default behaviour.
Something about "find back"
jaPBe stores now the start point of each search. With F4 you can jump back to the root of your search. jaPBe can store about 100 "jump backs". Also "goto line" and "find declaration" store there beginning position.
"Find back" take care about deleted lines and closed files.
Normaly it is usefull, when every "find next" is stored in this memory. So it can be set in the preferences, that only new searchs are stored. This is the default behaviour.
okay, you seam to be suffering with the same fault of PB I do, not using strings in threads are you ????
Sorry, I crashed
An attempt to read or write to/from an address to which that process isn't allow..
This may not be your fault, this could very well be PB itself.
Process Followed To Bug;
Installed Japbe
Installed NeededTools
Executed Japbe
Configured Japbe to my liking visually.
Compiled Billboard.pb (didn't run, didn't compile)
Exited Japbe
Executed Japbe - CRASH
-> Looked at task mannager
Found FccLnk.exe
Found LccLnk.exe
Terminated Both Tasks.
Executed Japbe - Success.
Sorry, I crashed
An attempt to read or write to/from an address to which that process isn't allow..
This may not be your fault, this could very well be PB itself.
Process Followed To Bug;
Installed Japbe
Installed NeededTools
Executed Japbe
Configured Japbe to my liking visually.
Compiled Billboard.pb (didn't run, didn't compile)
Exited Japbe
Executed Japbe - CRASH
-> Looked at task mannager
Found FccLnk.exe
Found LccLnk.exe
Terminated Both Tasks.
Executed Japbe - Success.
Not complete right.Inner wrote:okay, you seam to be suffering with the same fault of PB I do, not using strings in threads are you ????
Code: Select all
Procedure LinkerFix(dummy)
Repeat
a=FindWindow_(0,@"lcclnk.exe")
If a=0
a=FindWindow_(0,@"fcclnk.exe")
EndIf
If a
b=FindWindowEx_(a,0,"Button",0)
If b
ShowWindow_(a,#SW_SHOWDEFAULT )
setactivewindow_(a)
SetForegroundWindow_(a)
SetFocus_(b)
SendMessage_(b,#WM_KEYDOWN,32,3735553)
SendMessage_(b,#WM_CHAR,32,3735553)
SendMessage_(b,#WM_KEYUP,32,-1070006271)
EndIf
Else
Delay(5000)
EndIf
ForEver
EndProcedure
>Process Followed To Bug;
>Installed Japbe
>Installed NeededTools
>Executed Japbe
>Configured Japbe to my liking visually.
>Compiled Billboard.pb (didn't run, didn't compile)
>Exited Japbe
>Executed Japbe - CRASH
Did you exit japbe, before the compiler is ready?
>-> Looked at task mannager
>Found FccLnk.exe
My Fake-Linker
>Found LccLnk.exe
The original linker.
Both should be terminated, after compile is ready...
btw: Can't reproduce

>2. The editor that comes with PB IDE does the same thing itself, so this is a PB issuse I think.
Ok, than jaPBe isn't the problem.
Maybe you have a Virus or a Worm. Many problems while compiled are result of virus/worms (don't ask why, it is so).
A freeware (for personal use!) virusscanner
http://www.free-av.com/
Maybe you should delete PB and reinstall it (don't forget to save the "DataKey" in the compiler-directory!).
When this all don't help, your system is corrupted.
Btw: Which system do you have installed (and with which service-pack)?
Ok, than jaPBe isn't the problem.
Maybe you have a Virus or a Worm. Many problems while compiled are result of virus/worms (don't ask why, it is so).
A freeware (for personal use!) virusscanner
http://www.free-av.com/
Maybe you should delete PB and reinstall it (don't forget to save the "DataKey" in the compiler-directory!).
When this all don't help, your system is corrupted.
Btw: Which system do you have installed (and with which service-pack)?
I found some heavy bugs:
* Title of windows are now changed, when a diffrent Language is selected.
* repair "load block"
* Extended Styles (Debug command, PureBasic procedures)
(PureBasic procedures are all PureBasic/Userlibs procedures. API-Commands are not included! Also all Procedures in the definitons)
* repair "print"
Codetemplates
* Code repaired for PB 3.89
Cutter
* It should now be impossible, that a source is included twice.
* Title of windows are now changed, when a diffrent Language is selected.
* repair "load block"
* Extended Styles (Debug command, PureBasic procedures)
(PureBasic procedures are all PureBasic/Userlibs procedures. API-Commands are not included! Also all Procedures in the definitons)
* repair "print"
Codetemplates
* Code repaired for PB 3.89
Cutter
* It should now be impossible, that a source is included twice.
Nope, no worm, no virus (way to careful for that). but however I think the reason why you can't/don't see it, is because your LccLnk.exe wasn't updated when you install the 3.89b1 update, since this is the course of it.
I replaced the new LccLnk.exe with the old version pre-3.89 and it worked fine, this maybe why some people see it and others don't. I've no idea why all people don't get this, as the installer should be working properly.
I replaced the new LccLnk.exe with the old version pre-3.89 and it worked fine, this maybe why some people see it and others don't. I've no idea why all people don't get this, as the installer should be working properly.