PureBasic 3.89 Beta 1 - Public release

[KuschelTeddy82]

The same problem with Sprite3D here and on Epyx's PC. All have nVidia Cards and it worked with 3.81

[kenmo]

But 3D worked for you two?

[Polo]

nothing in 3d work with the beta on my computer (last version worked well)

[fsw]

Terrain & Texture examples never worked here (on 2 computers...)

[Dreglor]

aside from the problems people are having,
what can we expect in the next beta\version

[freak]

News: Release 3.89 Beta 1
-------------------------

- Added: CountString(), KeyboardInput(), GetWindowTitle(), SetWindowTitle(), ElapsedMilliseconds()
- Added: MDIGadget() by Fr34k
- Added: 'Static' keyword for local variable which need to be persistent
- Added: VerticalBlank support for FlipBuffers() (and works in windowedmode too)
- Added: RemoveGadgetColumn(), SetGadgetAttribute(), GetGadgetAttribute(), SetGadgetItemAttribute(), GetGadgetItemAttribute()
- Added: Autosize for StatusBar and ToolBar (no more callback needed)
- Added: New size handler by Fr34k which allow realtime window sizing without callback !
- Added: New 'z' optionnal parameter to TransformSprite3D()
- Added: Several new flags for SplitterGadget() for better flexibility
- Added: SetGadgetAttribute() support for ScrollAreaGadget() to resize the inner area.
- Added: Joystick and Module support for NT4 compatibility mode
- Added: Hexadecimal display, clear-copy-save debug output and window position saving to the debugger
- Added: Support for different depth icons for the default program icon
- Added: IDE features: Interface viewer, new MS SDK support, find in files, line numbering
- Added #PB_Any support for DataBase, File, Font, FileSystem, Gadget, Image, Library, Module, Movie, Palette, Sprite, Sprite3D, SysTray, ToolBar and StatusBar, Window

- Changed: no more #Memory ID and flag for AllocateMemory()

- Splitted Database, File, Network, StatusBar and Systray libraries

- Removed: UpdateStatusBar(), UseMemory()

- Fixed: NT4 (DirectX 3) support for Sprite, Palette, Sound, Keyboard and Mouse libraries
- Fixed: Bug in CreateSprite3D(), the width and size was 1 pixel wider
- Fixed: Bug with SpritePixelCollision if the same sprite was used for both collisions.
- Fixed: Bug in the debugger with win98 (application window was in background)

Timo

[Sveinung]

I get ..\debugger\debugger.obj.text:undefined reference to '_PB_DEBUGGER_PureBasicPath'

Anyone got the same problem

Sveinung

[ricardo]

I think that the help file is extremely important in a beta testing release, otherwise we need to figure alone how can a new command works!

IMHO makes no sense release a beta with no help file.

[PolyVector]

#Nevermind...hehe

[NoahPhense]

I think that the help file is extremely important in a beta testing release, otherwise we need to figure alone how can a new command works!

IMHO makes no sense release a beta with no help file.

You did let it update your current version, right? As for help files.. theres
always time for that.. most beta testers don't work from a help file.

I still have all my own stuff, help files an all:

Code: Select all

-------------------------------------------------------------------------------
PureBasic v3.89 Beta 1 Release - Read Me
-------------------------------------------------------------------------------
  This beta is for testing purpose only. Never assume it to be stable
  or even working. But, we provide it to public beta testing as we don't
  found any bugs anymore and want to be sure to have a correct product before
  release it. Be free to test it with all your program and reports
  any problem to the bug report section, with 'Beta - ' in the title.
  
  We strongly suggest to makes a whole copy of the 'PureBasic' folder
  and install this beta on it, to keep a working distribution. You have
  to install this beta over a regular PureBasic 3.81.
  
  This beta requiers the registered version of PureBasic.

We work off the release notes, and break stuff, then things
get fixed, and eventually, the help file is modified.

- np

[RJP Computing]

@Ricardo,
Remeber this is a beta release. If you want things to run smooth I wouldn't update to the beta. Wait a bit until it is at a level you feel is complete enough for you. This way you can be as productive as you want.

Just my $0.02.

[NoahPhense]

@Ricardo,
Remeber this is a beta release. If you want things to run smooth I wouldn't update to the beta. Wait a bit until it is at a level you feel is complete enough for you. This way you can be as productive as you want.

Just my $0.02.

I don't mind updating to the beta. As I backup the PB structure every
other day. So I'm keeping my 3.81 structure backup intact. Just in case.

- np

[freedimension]

@Ricardo,
Remeber this is a beta release. If you want things to run smooth I wouldn't update to the beta. Wait a bit until it is at a level you feel is complete enough for you. This way you can be as productive as you want.

Just my $0.02.

But ricardo said nothing about beeing unproductive or things that should run smoothly. The one thing he said though, is that it's quite hard to beta test a product if you don't know how to use new commands and features. In this point I totally agree with him.
If there is little feedback in a beta testing phase, this is one of the main reasons for it, as I perceive it.

[Sparkie]

I fully appreciate the efforts of Fred and the PB Team members in bringing us new and improved versions of PB. I'm not expecting to use this or any other beta release for productivity. I would simply like to help weed out any bugs. As an example:

- Added: Several new flags for SplitterGadget() for better flexibility

I would like to test the new SplitterGadget flags, but I have no idea what these new flags are.

[Fred]

That's true, I will post some examples to explain that.