Page 78 of 104
Re: Custom Icon not appearing
Posted: Fri Mar 13, 2009 11:28 am
by gnozal
RichardL wrote:Hi Gnozal,
If I go to 'File/Preferences' and select the 'Project' tab I am offered a field 'Use Icon'. I browse to an icon (thanks for the two starter icons) and select 'Open'. The path and icon name appear on the display. Good!
I then quit via the 'OK' button.
Restarting jaPBe brings back the contents of the 'Use Icon' field, so my choice was recognized.
When I next produce an executable it does NOT have the specified icon; should it, or am I doing something stupid (wouldn't be the first time!)?
Richard L
Hi Richard,
'File -> Preferences -> Project' should be used to set the default settings for new projects (File -> New).
For an existing project (File -> Open), use 'Project -> Options'.
I hope it makes sense.
Posted: Fri Mar 13, 2009 1:26 pm
by RichardL
Hi,
Thank you... now all OK.
"None so blind as those who do not look in the right place!" ... as my mother used to say
Richard
Posted: Tue Mar 17, 2009 5:13 pm
by Hurga
Hi gnozal
Maybe I do something wrong, but jaPBe dosnt autocomplete the procedures from the include-files.
I think It would be a helpful option, if jaPBe would autocomplete these procedures. Or maybe just these, which are check for the current sourcefile.
Any help or any chance to include this
Posted: Tue Mar 17, 2009 5:27 pm
by gnozal
Hurga wrote:Maybe I do something wrong, but jaPBe dosnt autocomplete the procedures from the include-files.
It doesn't, unless :
- the include file is loaded
or
- a
definition file exists and is loaded [see Preferences -> Definitions].
The definition files are located in %jaPBe%\Definitions ; you can create your own custom definition files, based on your custom includes, with 'Files > Save as definition'. See manual [Menu Overview -> File Menu -> Definitions].
Compiler Configuration issue in Editor jaPBe
Posted: Fri Mar 20, 2009 4:12 pm
by Peter_DevRes
Hi there,
I had a play with the jaPBe editor yesterday and really liked it.
I wanted to use it as my editor of choice but found my code wouldn't compile, the reason was in the PureBasicIDE editor there is an option I need but can't find in jaPBe:
In the traditional PureBasicID editor:
Compiler>Compiler Options>Constants> there is a parameter called '#PB_Editor_BuildCount' which I have ticked. I use this as in a procedure to display the software build number in the program I am developing.
When I run the compiler in jaPBe I get the following error 'Constant Not Found #PB_Editor_BuildCount on Line xxx' because I can't find the resiprical configuration option as per above in jaPBe.
Can anyone help? any ideas?
I either need to find another way to automatically insert the build number...(actually I do need to manually change the constant to increase the build number anyway, so I guess it may not be the best solution)
...or...
Find something like a 'Constant' option in jaPBe.
Thanks & Regards,
Peter
Re: Comiler Configuration issue in Editor jaPBe
Posted: Fri Mar 20, 2009 4:33 pm
by gnozal
Peter_DevRes wrote:When I run the compiler in jaPBe I get the following error 'Constant Not Found #PB_Editor_BuildCount on Line xxx' because I can't find the resiprical configuration option as per above in jaPBe.
Hi Peter,
The #PB_
Editor_BuildCount is a PB IDE specific constant.
In jaPBe, the build constant is named #jaPBe_ExecuteBuild.
The jaPBe constants are (from manual) :
Code: Select all
#jaPBe_ExecuteBuild : Build number
#jaPBe_CompilerVersion : PB compiler version
#jaPBe_OnError : If #True, OnError is enabled in Project Options
#jaPBe_IsDebuggerRunning : If #True, project is compiled with debugger
#jaPBe_IsExecute : If #True, compiled with "Create Executable" (else "Compile / Run")
#jaPBe_ExecuteType : Executable type (0 : Windows, 1 : DLL, 2 : Console)
#jaPBe_Compiler_File : Compiled source path + filename (like #PB_Compiler_File)
#jaPBe_SourcePath : Compiled source path
#jaPBe_SourceFile : Compiled source filename
A quick help is also available in the panel on the right side ('Help' tab)
Posted: Mon Mar 30, 2009 1:04 pm
by gnozal
Sirhc.ITI wrote:Hi, I found a little problem with the "Working Directory" entry of the Tools Section. The Standard IDE sets if working directory is empty, the path of the Sourcecode, but japbe dosn't.
So i have a little problem with one of my tools, i send them "%TempFile" but i want also read the includes, so i need that the working path is the path of the current sourcecode.
Did you try using two parameters for your tool : %TEMPFILE (to get the temp file) and %FILE (to get the source path) ?
Posted: Mon Mar 30, 2009 4:55 pm
by gnozal
Sirhc.ITI wrote:Yes, thats an option, but it would be nice if it would behave like the standard ide
Sure, it would be nice, but jaPBe is older than the actual PB IDE, so it may behave differently.
In this example, it's easy to add an extra case to your tool : if there is a second parameter (%FILE), assume it's jaPBe and act accordingly.
Anyway, I have uploaded a new build which should work as you expect.
Sirhc.ITI wrote:I can't say "run after Compile/Run" without saying "wait until tool quits", Why can't i use a trigger without waiting for a tool to quit?
I am sure there is (was ?) a good reason, but I can't remember it right now
One reason I can think of is to avoid problems when 2 or more tools are triggered at the same time : each one may want to modify the same file at the same moment. So waiting for a tool to be finished before starting the next tool makes sense, I think.
Posted: Fri Apr 10, 2009 7:55 am
by gnozal
Update (jaPBe 3.9.4 build 775)
Changes :
- use SDK help : you can now select the SDK ms-help v2 name space in a combobox (example : MS.PSDK.1033 for the Microsoft Platform SDK February 2003).
Notes :
. if you select "msdn.microsoft.com", jaPBe will search for the API function on the internet ;
. if your installed SDK namespace isn't listed in the combobox, you may add a namespace using AddSDKNameSpace in jaPBe.Pref (see manual).
- added a 'Make variable protected' feature : CTRL+L while carret is on variable. A 'Protected MyVar' is added on top of the current procedure.
- added sverson's plugin DisplaySystemMetrics plugin.
- manual updated.
Posted: Sat Apr 11, 2009 2:57 pm
by nicolaus
thanks for the update and you great work!
Posted: Wed Apr 22, 2009 1:34 pm
by gnozal
Update (jaPBe 3.9.4 build 779)
Changes :
- huge change in folding code : folding should now be _much_ faster.
Please report any problem in this thread.
Posted: Wed Apr 22, 2009 3:09 pm
by RichardL
Hi Gnozal,
I have just upgraded jaPBe to 779. The following line shows a problem... run the cursor along it and see it change!
Code: Select all
BangTime.l = Date(y.w,m.w,D.w,h.w,i.w,S.w) + (86400*10) ; Calculate the timestamp for JUST TEN Days hence
The problem occurs in the line is embedded in a large file... or on its own.
RichardL
Posted: Wed Apr 22, 2009 3:25 pm
by gnozal
RichardL wrote:Hi Gnozal,
I have just upgraded jaPBe to 779. The following line shows a problem... run the cursor along it and see it change!
Code: Select all
BangTime.l = Date(y.w,m.w,D.w,h.w,i.w,S.w) + (86400*10) ; Calculate the timestamp for JUST TEN Days hence
Hi Richard,
I don't see anything unusual while moving the carret along this line.
Could you be more specific ?
And what build did you use previously ?
Posted: Thu Apr 23, 2009 11:31 am
by RichardL
Hi,
My previous jaPBe was installed with <jaPBeFor PB400_391>
The effect was that the comment area of the line moved to the left so that it included part of the code... as indicated by the comment highlighting.
Yesterday the effect remained even if I closed jaPBe and re-opened it. I did this several times.
Today, after re-starting the computer I cannot reproduce the problem, but I have needed to fix a broken line or two on yesterday's source file; so it was not a figment of my imagination.
Best regards,
Richard
Posted: Thu Apr 23, 2009 1:08 pm
by gnozal
RichardL wrote:The effect was that the comment area of the line moved to the left so that it included part of the code... as indicated by the comment highlighting.
RichardL wrote:Today, after re-starting the computer I cannot reproduce the problem, but I have needed to fix a broken line or two on yesterday's source file; so it was not a figment of my imagination.
Ok, thanks. I tried hard on several sources of mine but I could not reproduce this issue.