PureBasic Forums - English

Great work (as always )

You certainly put alot of work into the product - thanks for all your work - looks great - Can't wait for the new VD also

Excellent work guys, as usual!!! Donation on it's way, also as usual

hehe,great work!

Okey, some improvements for the PureBasic team:

It says:

- Removed: StrQ(), HexQ(), BinQ(), ValQ()
- Removed: ChangeListIconDisplay(), replaced by a gadget attribute
- Removed: ButtonImageGadget() backward compatibility
- Removed: CreateGadgetList(), now automatically done in OpenWindow()
- Removed: CopyTexture(), TextureOutput()

Could you also tell the users what to use instead. Like the TextureOutput() was removed...yeah, great probably....but replaced with what? And most important, how can one now perform drawing on the texture? Where can I find information about commands that were removed..and how to perform the action in PB4.30

Also, the PB4.30 help file.... If one check the command for StartDrawing() one could find the TextureOutput() as a valid operator....only to find that in french language....while the rest of the manual is English....

And check the overview for 2DDrawing...its says:
[quote]The output of the drawing functions is possible on a window, a screen, a sprite, an image, a texture or the printer. More information can be found at StartDrawing(). [/quote]

Note the word "T E X T U R E"

Bad release I think. Not happy.

For Christ's sake. How can you say it's a bad release when all your complaints are about the help file?

My main concern is maybe not about the help file.

The main concern is that a command was removed without ANY clue of HOW to do it in the new release. If one remove a command, it should at least be some clue how to pull it off using a better, improved method (as always Purebasic progresses to the better in overall of course)

Look at the other other removed commands:
StrQ(), HexQ(), BinQ(), ValQ() = These can now be Str(Value.Q) = fine, says so in the manual
"ChangeListIconDisplay()" it says "replaced by gadget attribute" = fine
" CreateGadgetList()" = "now automatically done in OpenWindow()" = fine

"CopyTexture(), TextureOutput()" = ??? Replaced by what? How to do in PB4.30? Nothing...could at least say:

"Use LoadImage(), Draw on that, save that to disk, load that as new texture" or something as a workaround....

have to admit it's a bit rough

but it's maybe just the team that forgot to write it up in the doc

> CopyTexture(), TextureOutput()
they didnt remove it for fun. im sure that fred will implement it again, as soon as he finds a way around it.

c ya,
nco2k

Well, it's about time for the next release, isn't it? Hint hint

Minor point, but this release is written as four point thirty (4.30). Is that correct ? Should it be four point three (4.3 or 4.03). Since the release of version 4 I haven't seen the other 29 minor releases, if correct. Or should it be 4.0.0 -> 4.3.0, which I think is more technically correct. And I know everyone has their own opinion on versioning !

Despite its flaws, PB is getting better with every release - especially when it comes to portability across platforms. In particular, 4.30 was a real milestone in that area!

Now, I'm looking forward to 4.40 with the ability to produce DLLs, .so's and DyLibs - that would be another milestone!

Rozek wrote:Despite its flaws, PB is getting better with every release - especially when it comes to portability across platforms. In particular, 4.30 was a real milestone in that area!

Now, I'm looking forward to 4.40 with the ability to produce DLLs, .so's and DyLibs - that would be another milestone!

... ? You can produce DLLs right now ...

...but neither .dylibs nor .so's (I am not so sure about .so's, but generation of .dylibs is broken right now) Fred once wrote: "...dylib on OS X doesn't work for now. It's planned for 4.40." (see http://www.purebasic.fr/english/viewtop ... highlight=)

And one of the outstanding features of PB is its platform-independance!

As we all can see oakvalley is completely right, however that is far to be a good reason to say 4.30 is a bad release.
In fact there is not a good reason to say such a thing, even there are still some scaring bugs (bugs that hopefully are ignored by oakvalley ).