PureBasic Forums - English

Psychophanta wrote:In the Hex() for example manual wrote:

'Type' can be:
#PB_Byte : The value is a byte number, ranging from 0 to 255
#PB_Ascii : The value is a ascii character, ranging from 0 to 255
#PB_Word : The value is a word number, ranging from 0 to 65536
#PB_Unicode: The value is a unicode character, ranging from 0 to 65536
#PB_Long : The value is a long number, ranging from 0 to 4294967296
#PB_Quad : The value is a quad number, ranging from 0 to 18446744073709551615

and should be:

'Type' can be:
#PB_Byte : The value is a byte number, ranging from 0 to 255
#PB_Ascii : The value is a ascii character, ranging from 0 to 255
#PB_Word : The value is a word number, ranging from 0 to 65535
#PB_Unicode: The value is a unicode character, ranging from 0 to 65535
#PB_Long : The value is a long number, ranging from 0 to 4294967295
#PB_Quad : The value is a quad number, ranging from 0 to 18446744073709551615

or still better imo:

'Type' can be:
#PB_Byte : The value is a byte number, ranging from 0 to $FF
#PB_Ascii : The value is a ascii character, ranging from 0 to $FF
#PB_Word : The value is a word number, ranging from 0 to $FFFF
#PB_Unicode: The value is a unicode character, ranging from 0 to $FFFF
#PB_Long : The value is a long number, ranging from 0 to $FFFFFFFF
#PB_Quad : The value is a quad number, ranging from 0 to $FFFFFFFFFFFFFFFF

Debug $FF                 ; will give 255
Debug $FFFF               ; will give 65535
Debug $FFFFFFFF           ; will give 4294967295
Debug $FFFFFFFFFFFFFFFF   ; will give -1

Captn. Jinguji wrote:Hi Andre.
It is only a minor thing, you decide whether it is worthwhile adding a hint to the docs:
Plz view this thread Compiler options and Create Executable

blueznl wrote:The Survival Guide contains some stuff on type casting and expression evaluation and migth be converted to a more official document, however the rules once sanctioned seem to be still a little broken, or I simply do not understand the new rules... Yet, it may provide a starting point, and the PB team is free to use them.

Comtois wrote:About LoadTexture() i can read this in the doc :

Texture format can be in PNG, TGA or JPG.

In Ogre.log i can read this

Supported formats: bmp,ico,jpg,jif,jpeg,jpe,koa,iff,lbm,pbm,pbm,pcd,pcx,pgm,pgm,png,ppm,ppm,ras,tga,targa,tif,tiff,wap,wbmp,wbm,psd,cut,xbm,xpm,dds,gif,g3,sgi,j2k,j2c,jp2

I tested different formats (bmp, gif, png, jpg, ico), they work very well, but does that all the formats mentioned above also work with PureBasic ?

The doc should be updated according to the formats supported.

Kaeru Gaman wrote:suggested improvement:
a little example to ResizeGadget() could show how a Gadget is moved, then it could be found with searching the Help for "move gadget"...
parallel to "windows.pb" that shows ResizeWindow and can be found via "move window".

Kaeru Gaman wrote: Help \ WindowedScreen \ Example 2
http://www.purebasic.com/documentation/ ... creen.html

Code: Select all

; we don't need exact screen width/height, because it will be automatically stretched...

this is wrong!
it's about a dozen times know I answer this question to beginners, I wrote about a dozen times in the forums that the example is wrong.

....

in the german Help for 4.40 the coordinates are corrected to 320x200, but the misleading comment is still in it.

luis wrote:http://www.purebasic.com/documentation/ ... chive.html

(e.g. texture, mesh, sky, @link""RenderWorld" "world")

tag link malformed

luis wrote:In the GOTO help

"To exit a loop savely" should be "safely" I presume.


maybe it would be nice to write in the help it's not safe to exit a select case using a GOTO.
...
this is suggesting to me the select-case is using the stack, so a jump out of it would leave the stack unbalanced.
...
In that case better to resort to if-elseif-endif if one really want to use a goto for some reason.

luis wrote:OnErrorGoto
http://www.purebasic.com/documentation/ ... rgoto.html

It is also not save to continue

save -> safe

luis wrote:ArraySize()

@arraysizereturns -1, if the array couldn't be declared (out of memory...).

Should be "ArraySize() returns -1, ..."

GG wrote:Sorry if this error is already mentioned, but for DatabaseUpdate() in chm help file (databaseupdate.html) , the example doesn't mention 2 param, only one (the db handler is ommitted).
.... corrected as :
DatabaseUpdate(#database,"UPDATE employee SET checked=1 WHERE id="+GetDatabaseString(#Database, 0))

Little John wrote:In PB 4.41 RC 1, in the help for WaitWindowEvent(), it reads in the example:

Code: Select all

    Case 3 : Debug "Button 3 clicked!"

Andre wrote:Is the last one right?

Andre wrote:Added a example line of code + additional comment about moving the gadget...

Andre wrote:Misleading comment removed.

Kaeru Gaman wrote:

Andre wrote:Is the last one right?

yes it is, because PB only knows signed variables.
since there is no bigger container (yet), PB can only debug Quads.
any smaller value can be displayed seemingly unsigned, because it displays the Quad-Container.

Debug StrU($FFFFFFFFFFFFFFFF) ; =18446744073709551615

Note: This function isn't mandatory when dealing with maps, as elements are automatically added when affecting a value to them

You can add as many elements as you want (or as many as will fit into the memory of your computer), and accessing it back using a key.

Statusbar-Help wrote:ATan(Angle) Returns the Arc-Tangent of the specified angle, in radian.

ATan() Help Doc wrote:Returns the arc-tangent of the specified value. Value.f can be any value, the result will be in radians.

Width and Height should be standard combinations: 640*480, 800*600, 1024*768...

Width and Height have to make up a supported resolution. The combination of Width, Height, Depth and RefreshRate is called a ScreenMode.
The ScreenModes the Hardware supports can be found out using ->ExamineScreenModes().

This program cannot display the webpage