nicolaus wrote:... and after that i have no code in a tab but i can hear a long time the sound what comse normaly only if i declare a new variable or so.
If you here the sound like for a new variable, you should also see 'Neue Variable:xxxx' in the info box ; is this the case ?
I start jaPBe (3.8.12.746) ['Bei neuem word abspielen' enabled]
I open TEST_Include.pb, it also opens the 4 TEST_Include_X.pb files.
I close TEST_Include.pb, it also closes the 4 TEST_Include_X.pb files.
And no sound nor 'Neue Variable:xxxx' in the info box.
For free libraries and tools, visit my web site (also home of jaPBe V3 and PureFORM).
I just switched over from VB.net and PowerBASIC to using PureBasic 32/64 bit versions. I love PureBasic and wanted to give jaPBe IDE a try out. However, I don't know where to get instructions on how to install the jaPBe manual, or other extensions to the IDE.
I would appreciate any suggestions because the jaPBe looks like a great IDE for PB.
Logman wrote:I just switched over from VB.net and PowerBASIC to using PureBasic 32/64 bit versions. I love PureBasic and wanted to give jaPBe IDE a try out. However, I don't know where to get instructions on how to install the jaPBe manual, or other extensions to the IDE.
I would appreciate any suggestions because the jaPBe looks like a great IDE for PB.
Welcome to Purebasic !
1. Install jaPBe : extract jaPBeForPB400_3812.exe in some directory.
I install it in a subdir of the purebasic directory.
2. Start jaPBe.exe ; you may have to set the compiler path in preferences.
3. Manual : extract jaPBeForPB400_Manual.7z to jaPBe\Language\
4. Plugins : extract them to jaPBe\Plugin\
5. Tools : install them in some directory and add the path + parameters in Main menu -> Tools -> Config Tools
For free libraries and tools, visit my web site (also home of jaPBe V3 and PureFORM).
Outstanding. Thanks for the quick help. I've got to hand it to you an the PureBasic folks. I started right in using PureBasic and both IDEs because they were so well thought out and intuitive. I only had to about an hour reading the PureBasic manual to get jist of how to define variables using the PureBasic format.
What a great compiler system, especially the 64-bit version.
I have updated the Registry.pbi again, it did not close the RootKey Handle and therefore there was a big Handle-leak. I also added my new PList.pbi that supports the reading and manipulating of Max OS X's PList files (XML format).
Best regards
Last edited by mback2k on Sun Jun 05, 2011 7:22 pm, edited 1 time in total.
mback2k wrote:I have updated the Registry.pbi again, it did not close the RootKey Handle and therefore there was a big Handle-leak. I also added my new PList.pbi that supports the reading and manipulating of Max OS X's PList files (XML format).
Thanks, archive updated
For free libraries and tools, visit my web site (also home of jaPBe V3 and PureFORM).
Anyone else get an infection warning from their AV software and jaPBe 3.8.12
My AVG (with latest updates) is reporting Win32/Heur in jaPBe.exe. I'm sure it's a false positive but I would find it hard to believe if I'm the only one with this issue.
You can send this file to this link which uses several anti virus engines to check it. http://virusscan.jotti.org/
I sent the same file you asked about that I had downloaded and it shows clean.
That's not to say that your is. Because an infection could have occured at a
different time in which you downloaded it.
Just check it out there. At least it should make you feel a little more
comfortable using it.
Sparkie wrote:Anyone else get an infection warning from their AV software and jaPBe 3.8.12
My AVG (with latest updates) is reporting Win32/Heur in jaPBe.exe. I'm sure it's a false positive but I would find it hard to believe if I'm the only one with this issue.
I had the same issue and just had AVG ignore the directory where I installed jaPBe (figured it might happen again on future updates). I downloaded directly from gnozal's site and didn't see any posts of any virus issues in the forums so I didn't think it was anything real (plus I didn't get any warnings from ESET when I installed on my laptop)...
If i compile the code from the function OpenWindowedScreen() of the help file (go to OpenWindowedScreen() in the help file) that the compiler say that at the line 11
nicolaus wrote:If i compile the code from the function OpenWindowedScreen() of the help file (go to OpenWindowedScreen() in the help file) that the compiler say that at the line 11
Looks more like a debugger message ?
I can't confirm this. I just compiled the code (copy/paste from help file) without an error / warning with jaPBe 3.8.12.746 - WinXP - PB4.30 final.
nicolaus wrote:If i compile the same code with the original IDE it works very well.
jaPBe uses the external debugger. Did you try it with the PB IDE ?
For free libraries and tools, visit my web site (also home of jaPBe V3 and PureFORM).
nicolaus wrote:If i compile the code from the function OpenWindowedScreen() of the help file (go to OpenWindowedScreen() in the help file) that the compiler say that at the line 11
Looks more like a debugger message ?
I can't confirm this. I just compiled the code (copy/paste from help file) without an error / warning with jaPBe 3.8.12.746 - WinXP - PB4.30 final.
nicolaus wrote:If i compile the same code with the original IDE it works very well.
jaPBe uses the external debugger. Did you try it with the PB IDE ?
Hi Gnozal
Yes i have test it with PB IDE and it works fine with the PB IDE.
I have test it with Vista 32 bit and XP SP3 and with all the systems i have the same result.
With the PB IDE it works and with jaPBe a see the error.