PureBasic Forums - English

Chr()

In the help of PB 4.40 Beta 3 it reads like this:

Text$ = Chr(ASCII-Value)
Returns the character associated with the given ASCII value.

Not a single word about Unicode there ...
But Chr() can also return Unicode characters (in unicode mode, if the source file is in UTF8 format). That's much appreciated and pretty cool, but before we can use it, we'll have to know about it.
So mention it in the docs, please.

Regards, Little John

NewMap

Although the help for NewMap() exists, the word "NewMap" does not appear in the help index. Also in the command index of Map(), the word "NewMap" is missing.

Another mistake:
In the beginning of the second paragraph of the English help for NewMap it reads

When using a new key for an affection, a new element is automatically added to the map.

"affection" doesn't make sense in this context. In the German help, it correctly reads "Zuweisung" here. This is "assignment" in English.

Regards, Little John

The link to TextureOutput() in StartDrawing() should be removed.

@Little John:

The spelling error in english 'NewMap' help was fixed, as well a false link to the 'LinkedList' library in the introduction of the 'Map' library. There is also a link to the 'NewMap' keyword already there.... and it's not listed in the command-list of this library just because it's a keyword and not a command of this library.

The other issues I've set on the 'ToDo' list - see first post...

Arctic Fox wrote:The link to TextureOutput() in StartDrawing() should be removed.

Done.

Thank you, Andre!

Regards, Little John

I'm using beta5 and the CHM has no documentation of the new 2D Drawing commands, drawing modes, etc.

It would be helpful if the manual explained the For:Next command a little better..

e.g. Stepping and negative stepping for example. --blueb

blueb wrote:It would be helpful if the manual explained the For:Next command a little better..

e.g. Stepping and negative stepping for example.

Code: Select all

k = 10
For k = 10 To 1 Step -1
    Debug k
Next

Done

Seymour Clufley wrote:I'm using beta5 and the CHM has no documentation of the new 2D Drawing commands, drawing modes, etc.

Set on ToDo list for Fred/freak.

FillArea()

Currently the Reference Manual writes:

If the 'BorderColor' parameter is set to -1, then the area defined by the color found at the (x,y) coordinates will be filled.

IMHO this hardly describes the effect of -1 in this context.

I think it should read something like this:

If the 'BorderColor' parameter is set to -1, then any color that is different from the color at point (x,y) will be treated as 'BorderColor'.

Regards, Little John

Hi,

DatabaseUpdate() needs an update!

At the weekend I was fighting for ours with SQLite and the example in the (german) help.
This example tells you, that it is possible to update each entry in the database inside the loop.
But it is not working.

There is already a posting about that, but nothing is changed.
http://www.purebasic.fr/english/viewtop ... te#p248148

So please change the helpfile, or if it is a bug with SQLite, write it inside this help.

Best regards,

Bernd

Hi, it would be helpful to have a better explanation of the different screen output subsystems and which commands are supported by each subsystem. Also a compiler warning would be nice, if you try to use an unsupported command.

As I posted in the "Coding questions" section a few days ago, some example code in the current help regarding 2D drawing ( see e.g. Circle() ) does not work at all on Ubuntu.

Srod has confirmed my point of view and nobody objected, so I really think the example code is wrong, at least as far as Linux is concerned.
On Windows, the example code in the help does work, but srod wrote that in his opinion the modification that I posted (suggested by #Null on the German forum) is the safer one to use on all platforms.

Since it's important to have working example code, please change it for the 4.40 final release.

TIA, Little John

Little John wrote:If the 'BorderColor' parameter is set to -1, then any color that is different from the color at point (x,y) will be treated as 'BorderColor'.

I strongly agree with this suggestion.

would be nice if you could re-arrange the value types table and keep .c at one place.

currently:

Byte
Ascii
Character
Word
Unicode
Character
Long
Integer
Integer
Float
Quad
Double
String
Fixed String

better:

Byte
Ascii
Word
Unicode
Character
Character
Long
Quad
Integer
Integer
Float
Double
String
Fixed String

btw, why isnt there a default (.i like) type for floats? .f on 32bit and .d on 64bit. isnt .d 'faster' on 64bit?

c ya,
nco2k