PureBasic Windows 3.94 beta 1 released!
@ Fred & Co
Congratulations.
A downside of the new Editor is it's size (800kb) and it seems to be slower than the old one, but hey you can't have it all I guess...
Question:
How to close the output-window and the explorer/procedure-window?
Bug:
The Callstack Viewer is really cool, but if I press on the update button and go with the mouse cursor over the compiled app the editor crashes.
Tested on WinXP-PRO-SP2/P4HT-3Ghz-1.5GbRam
Congratulations.
A downside of the new Editor is it's size (800kb) and it seems to be slower than the old one, but hey you can't have it all I guess...
Question:
How to close the output-window and the explorer/procedure-window?
Bug:
The Callstack Viewer is really cool, but if I press on the update button and go with the mouse cursor over the compiled app the editor crashes.
Tested on WinXP-PRO-SP2/P4HT-3Ghz-1.5GbRam
-
- Enthusiast
- Posts: 767
- Joined: Sat Jan 24, 2004 6:56 pm
Can this beta be installed with 3.93 on the same machine?
EDIT: the readme says it all. Sorry for shooting from the hip...
EDIT: the readme says it all. Sorry for shooting from the hip...

Last edited by dell_jockey on Fri Jun 03, 2005 10:11 pm, edited 1 time in total.
J.Baker: disable the IDE debugger, what do you mean ? you can choose which debugger to use in the preference panel.
fsw: the size it bigger for several reasons (much more features, scintilla component (+150 kb), internal viewer which uses the image decoders (+200 kb) and of course the debugger). So all in all, it's not a bad size for a such tool. About the speed, i don't understand as the scintilla component is much more faster than the old richedit one.
dell_jockey: The beta can be installed on the same machine. Be sure to copy your whole purebasic directory and install it in.
fsw: the size it bigger for several reasons (much more features, scintilla component (+150 kb), internal viewer which uses the image decoders (+200 kb) and of course the debugger). So all in all, it's not a bad size for a such tool. About the speed, i don't understand as the scintilla component is much more faster than the old richedit one.
dell_jockey: The beta can be installed on the same machine. Be sure to copy your whole purebasic directory and install it in.
[quote="Fred"]J.Baker: disable the IDE debugger, what do you mean ? you can choose which debugger to use in the preference panel.[quote]
When I choose the GUI Debugger, the Integrated Debugger (window box at bottom of PB) doesn't go away. Sorry, I just find the Integrated Debugger annoying.
When I choose the GUI Debugger, the Integrated Debugger (window box at bottom of PB) doesn't go away. Sorry, I just find the Integrated Debugger annoying.
www.posemotion.com
PureBasic Tools for OS X: PureMonitor, plist Tool, Data Maker & App Chef
Even the vine knows it surroundings but the man with eyes does not.
PureBasic Tools for OS X: PureMonitor, plist Tool, Data Maker & App Chef
Even the vine knows it surroundings but the man with eyes does not.
This is an incredible preview of where PB is going, and I am loving what I am seeing. However, I'm going to put my critical hat on for a second.
The new IDE has a little way to go to catch up with jaPBe. Having to press ctrl-space is a nuisance, the jaPBe autocompletion is always there.
Much more exciting is the Debugger, which is a huge improvement on the old. Superb.
The Memory viewer is another great new addition.
Some issues:
Reliability: The IDE keeps crashing, leaving behind the compiler's process. I tried to find some guaranteed to crash the debugger scenarios to report, but it seems to be slightly random. It become especially flaky when stepping through the debugger.
IDE Options: The IDE option comments are visible at the bottom of the page, and are sometimes repeated after a save.
Menus while debugging: When debugging the menus are greyed out, though the debugging menu is obviously available.
Some requests:
It would be nice to have an 'After Commented' trigger for the tools, which will pass the commented ASM to the tool, and then process the response just like the /REASM option on the command line.
The option of a Debug toolbar would save having to keep using the menu.
Working out the start and end of a memory range is a pest. Could the to option accept a relative argument like '+200' so that '1600 - +200' would be identical to '1600 - 1800'?
It would be good if the Debugger had a tab of allocated memory areas that lists the location and size of allocated blocks. Double clicking on one could open the memory viewer for that range. This would be very useful for tracking memroy leaks.
Please don't get me wrong, this is one amazing, exciting preview.
The new IDE has a little way to go to catch up with jaPBe. Having to press ctrl-space is a nuisance, the jaPBe autocompletion is always there.
Much more exciting is the Debugger, which is a huge improvement on the old. Superb.
The Memory viewer is another great new addition.
Some issues:
Reliability: The IDE keeps crashing, leaving behind the compiler's process. I tried to find some guaranteed to crash the debugger scenarios to report, but it seems to be slightly random. It become especially flaky when stepping through the debugger.
IDE Options: The IDE option comments are visible at the bottom of the page, and are sometimes repeated after a save.
Menus while debugging: When debugging the menus are greyed out, though the debugging menu is obviously available.
Some requests:
It would be nice to have an 'After Commented' trigger for the tools, which will pass the commented ASM to the tool, and then process the response just like the /REASM option on the command line.
The option of a Debug toolbar would save having to keep using the menu.
Working out the start and end of a memory range is a pest. Could the to option accept a relative argument like '+200' so that '1600 - +200' would be identical to '1600 - 1800'?
It would be good if the Debugger had a tab of allocated memory areas that lists the location and size of allocated blocks. Double clicking on one could open the memory viewer for that range. This would be very useful for tracking memroy leaks.
Please don't get me wrong, this is one amazing, exciting preview.
Hello,
As I said on franch forum, GREAT!
But, alwais but
there is a problem. When, in the Compiler options, I shoose to include the version informations, when compiling, I have error from porc "Synthax error" for version informations keywords. And still in the compiler option window in Version Informations tabe, when I press Tab for going to the next gadget, after Version Description, tha tab do the same as there would be others gadget after and a long time after, I have the button OK. Is it me again?
Thanks again for this beta.
As I said on franch forum, GREAT!

But, alwais but

Thanks again for this beta.

Yeah I agree 
One thing I'd love to see is some more stuff to the browser gadget.
More functions, maybe a integrated way of getting the url when the mouse hovers over a link so it can be displayed in the statusbar, also, a way of sending and retreiving more stuff using the webgadget. So we could create a real browser with plugin support
hgehehehe

One thing I'd love to see is some more stuff to the browser gadget.
More functions, maybe a integrated way of getting the url when the mouse hovers over a link so it can be displayed in the statusbar, also, a way of sending and retreiving more stuff using the webgadget. So we could create a real browser with plugin support

I Stepped On A Cornflake!!! Now I'm A Cereal Killer!
- Joakim Christiansen
- Addict
- Posts: 2452
- Joined: Wed Dec 22, 2004 4:12 pm
- Location: Norway
- Contact: