AddWindowStyle (W, S, F)

Enables one (or more) Windows Extended Window flags and flags, and thus changes the appearance of a window.

W: Long - Handle of a window, or (forB. HWnd%) or a control (forB. box)

S: Long - the value (s) for Window Style (s), or Extended window style (s)

Q: Long - flag, which styles are used: 0 = Window-Style / 1 = Extended Window Style

Score: 0

This looks like a window can be changed, which is already open. AddWindowStyle () adds

this, the specified Style with S added. This can have a combination of multiple window

His styles. However, the standard Windows styles may not with the extended window styles

be combined! If they want more one (or) extended window style (s) to add, then

must be specified for F is 1, for standard Windows styles a 0

Examples:

(1. Adds Profanfenster a horizontal and vertical scroller added)

(2. Adds a list box adds a window frame and makes the window a tool window. Yes, you really!)

Window 0,0-800,600 'Example 1

AddWindowStyle (% hwnd, $ 300000.0) '(both Scroller add)

(listbox% = Create "listbox", hwnd%, "", 176,8,496,368)

Example 2

AddWindowStyle (% listbox, $ C00000, 0) '(add borders)

AddWindowStyle (listbox%, 1,1) '(tool WindowStyle Trail)

SetText% listbox, "This' is still a list box!" '(Window title set)

Alpha Trans (F, X, Y, B1, B2, M)

Mixes two different images transparent one, this is a mask bitmap of the

Transparency level determined for both pictures.

Q: Long - Handle of the target bitmap (HDC) or 0

X: Long - X offset to the screen

Y: Long - Y offset to the screen

B1: Long - First one with a handle

B2: Long - Second handle with a generated PngToFX (), InitFX () or CreateFX () byte array (2. source bitmap)

M: Long - one with a handle PngToFX (), InitFX () or CreateFX () generated byte arrays (mask bitmap)

Result: Long - 0

The graphics of images B1 and B2 are combined, taking into account the mask bitmap M to F.

X and Y specify the upper left corner where they have placed both images. The size of the display

Rectangle is derived from the size of the bitmap that is specified in InitFX () / CreateFX (). The size

of B1, B2 and M, but must always be the same size!

For F can be either one of the most profane bitmaps (% HDC% HDC2 ...) are specified, or one with

Produced LoadFileImage () / CreateImage () was. If for F given a 0, then the expenditure is

not in a HDC, but in the byte array B1!

The data in the byte arrays, B1, B2 and M are not changed by calling Alpha Trans (), it was

then, for F 0 is specified. But even then, only B1 is changed. Otherwise Alpha Trans operates internally

with a fourth memory area.

The mask bitmap M should have a black-gray-white and his image. There are, however, also colored

Mask bitmaps achieve amazing effects.

The more white a pixel in the mask bitmap, the more visible, the pixels of source bitmap 1 (B1). Depending

darker a pixel in the mask bitmap is, the more visible, the pixels of source bitmap 2 (B2).

Two examples of trans-alpha () are in the ProSpeed source code folder.:

AttachSprite (H, ZH, XO, YO)

Sprite H attempts are automatically promoted to the position, which is located at the Sprite ZH moment, by far the XO, YO.

H: Long - one with a handle

ZH: Long - one with a goal-Handle

XO: Long - X Offset, X-distance to the target sprite

YO: Long - Y Offset, Y Offset goal Sprite

Result: Long - 0

With this function you can realize how great sprite effects, and with little user effort.

In order forPresented as a worm, several Sprite (perhaps chained balls) with AttachSprite ()

will. These hunts Sprite 1, after the sprite 2nd 3 behind Sprite Sprite 2 ago, 4 behind 3, etc., all with

small distance. Now just need sprite 1 are moved, and the other sprites move

wormlike automatically afterwards. It should, however, will have all the sprites, the same speed.

To unlock the Attach for Sprite H again, must be a given zero for ZH:

AttachSprite (attachsprite &, & sprite, 10,10)

...

AttachSprite (attachsprite &, 0,0,0) 'Attachmodus quit again

AttachSpriteAnim (H, ZH)

Enlargement

H: Long - one with a handle

ZH: Long - one with a goal-Handle

Result: Long - 0

Very suitable forAs for Jump & Run Games. When in a level more similar-looking enemies

there, they can very easily using AttachSprite () / AttachSpriteAnim () can be realized.

To attach the repeal of Anim Sprite H again, must be a given zero for ZH:

AttachSpriteAnim (attachsprite &, sprite &)

...

AttachSpriteAnim (attachsprite &, 0) 'Attach-Anim-stop mode again

BitBltArray (Z, X1, Y1, B, H, Q, X2, Y2, F, V)

Copies a rectangular portion of a byte array to another. If necessary, with or with transparent color mask.

Z: Long - one with a goal-Handle

X1: Long - left coordinate in the destination array

Y1: Long - the upper coordinate of the target array

B: long - width of the rectangle to be copied

H: Long - height of the rectangle to be copied

Q: Long - one with a spring handle

X2: Long - left coordinate in the source array

Y2: Long - the upper coordinate in the source array

Q: Long - Flag

V: Long - additional variable for certain flag F.

The rectangular section of the source array starting at X2, Y2 of a width of W pixels and a height

has H pixels, then the position X1, Y1 copied into the target array.

Aims to determine the last parameter Q, copies of which mode. If F = 0, then the square will

Area normally copied.

If F = 1, then it must be specified in V a transparent color, suchAs RGB (255,255,255). If a

Pixels in the source image that color, it is not copied into the target.

Another flag has the value 2 If F = 2, then it must specify in a V, another handle of a byte array

will. V is a mask image and determines whether the pixel color of Z or Q to dominate. Is

Pixel value in V = 0 (black), then the pixel color of the source is used. If V = 255 (white), then the

Pixel color of the target used. If V = 127, then the source and destination colors are mixed in equal parts

used. The blacker a pixel in the mask is, therefore, the dominant source of color, depending on white, the

dominant target colors

Important! If F = 2, then the mask image showing the size W x H must have!

Miscellaneous clipping (graphics go) on edges must also be prevented by user himself. The

Examines the function fails.

Black White (F, X, Y, B, P)

Turn a graphic on the screen (or parts thereof) of black and white image.

Q: Long - Handle of the target bitmap (HDC) or 0

X: Long - X offset to screen

Y: Long - Y offset to screen

B: Long - one with a handle

P: Long - the priority of the effect, 0-255 (127 = normal)

Result: Long - 0

The graphics of the screen is transformed into a black and white image. X and Y enter the upper left corner

to, from where the screen is black with white made. The size of the rectangle resulting from the size

the bitmap that InitFX was specified in () / CreateFX ().

If they call Black and White () inside a loop with varying priority, gives a very

amazing effect!

The lower the priority is, the more predominant the color black, the higher it is, the more predominant

the color white.

For F one of profane can either be specified or a bitmap, with LoadFileImage () /

CreateImage () was created. If passed, but for R 0, the function will be executed but

not brought to the screen.

Black White () is pretty fast and works in real time. Generally, the smaller the area, the faster

work function.

Before the function can be used, must be a preparation with InitFX () have taken place.

The data in the byte array B are produced by calling this function does not change.

= array & InitFX (exhdc &) 'Handle (byte array) to create a bitmap

Black and White (% HDC, 0.0, & array, 127)

FreeFX (array &) 'later release

Blur (F, X, Y, B)

Blurs the image on the screen (or any part thereof).

Q: Long - Handle of the target bitmap (HDC) or 0

X: Long - X offset to the screen

Y: Long - Y offset to the screen

B: Long - one with a handle

Result: Long - 0

The graphics of the screen is blurred. X and Y specify the upper left corner, from where the screen

is obliterated. The size of the blurring of the rectangle resulting from the size of the bitmap in

InitFX () / CreateFX indicated () was.

For F one of profane can either be specified or a bitmap, with LoadFileImage () /

CreateImage () was created. If passed, but for F 0, the function will be executed but

not brought to the screen.

Blur () is pretty fast and works in real time. From a 600 processor and a large should

Screen liquefy blurred.

Generally, the smaller the area, the faster works blur ().

Before the function can be applied must be a InitFX preparation with () have taken place.

The data in the byte array B are changed by calling this function ..

Example:

= array & InitFX (exhdc &) 'Handle (byte array) to create a bitmap

WhileLoop 256

Blur (% HDC, 0.0, array &)

EndWhile

FreeFX (array &) 'later release

BringSpriteToBottom (H)

Put a sprite in the presentation layer (layer completely down).

H: Long - one with a handle InitSprite () generated sprites

Sprite H will be made against all other sprites in the background and can therefore by any

Sprite others are masked.

An exception is generated, the first sprite, it always remains at the lowest level of representation

must.

BringSpriteToTop (H)

Sets a sprite in the presentation layer (layer completely) up.

H: Long - one with a handle InitSprite () generated sprites

Sprite H will be made against all other sprites in the foreground and can therefore by no

other sprite longer be covered.

Never use the first generated sprite!

ChangeBytesToWords (Q, A1, Z, A2, N)

Converted some or all of the bytes into an area to Word.

An overlap between source and target area is not advisable to use two different areas,

or different sections within an area. Still to remember is that the target area twice

must be as large as the source region, as two bytes containing a word yes.

Q: Long - the source address (egB. range variable)

A1: Long - Offset to the source address

Z: Long - target address (egB. range variable)

A2: Long - offset to the destination address

N: Long - Number of bytes to be converted to Words

Result: Long - 0

Example:

ChangeBytesToWords (area #, 0, field #, 20000.10000)

follows:

Address: 0 1 2 3 4 5 ... 20000 20002 20,004

20006 20008 ...

Value: 111 111 111 111 111 111 ... 111 111 111 111

111

Execution time, 40000 bytes:

Original Secular = 7010 milliseconds

ProSpeed.dll = 1 millisecond

Change Display (X, Y)

Changes the screen size without saving it.

Just for one game often requires a screen resolution of z.Example, 1024 x 768 For most

Users, but the screen is set at 800 x 600th With Change Display (), the resolution may be short

be changed just once, and then back again.

Oops, from 2.1 ProSpeed Change Display () can be called with the parameters 0.0. The

ie, the original Windows screen mode, then restored, as the user him in

System has saved. Therefore now no need to store and oldy oldx & & and the original

Frame rate is also restored.

What is new in version 2.7, which is attempted for each mode to obtain the set frame frequency. And

during downshifts of the screen will now no longer the window sizes of other programs changed!

X: Long - Width of the new screen resolution

Y: Long - the amount of the new screen resolution

Results: Long - Error code (0 = no error, otherwise MS_Win32.hlp, Change Display Settings ()), see

Example:

...

Change Display (1024.768) 'screen to 1024 x 768 setting

...

Change Display (0,0) 'screen to revert to the original Windows values

ChangeLongSequence (B, A)

Reverses the order of the long integer into Area B.

B: Long - range variable, table LongInt values

A: Long - Number of bytes that are affected in the reversal (smooth divisible by 4 of course!)

Result: Long - 0

For example, to change the sequence of long values in range of #. From: 8, 167,800, 56000, 45 would be 45, 56000, 167,800, 8

ChangeLongSequence (area # 16) '16 = 4 Long's a 4-byte, 4 x 4 = 16

ChangeSpritePara (H, P, V)

Change the various settings manually, a sprite) (only for professionals.

H: Long - one with a handle

P: Long - offset of the parameter

V: Long - New variable for parameter P

Result: Long - 0

For V LongInteger be expected. Here's a list of parameters for which new variables would be useful:

Offset importance

0 HDC the sprite bitmap, where the sprite data store "

4 X offset into the sprite HDC

8 Y offset into the sprite HDC

70

56 the HDC Secular window

68 HDC of Double-Buffer copy 1

84 HDC of Double Buffer Copy 2

92 mode, the background not scroll 0 = / 1 = Scroll

96 X pixels to scroll background

100 Y pixels to scroll background

156 Sprite number marking

312 starting point for MoveSpriteWithTable ()

For example, to assign a new sprite bitmapped data from another HDC inclusive of new offsets:

ChangeSpritePara (handle &, 0, & newhdc)

ChangeSpritePara (handle &, 4, & newx)

ChangeSpritePara (handle &, 8, & newy)

ChangeWordsToLong (Q, A1, Z, A2, N)

Transformed to some or all the Words in a field trip to Long.

An overlap between source and target area is not advisable to use two different areas,

or different sections within an area. Still to remember is that the target area is four times

must be as large as the source region since a long as two successive Words (includes 4 bytes).

Q: Long - the source address (egB. range variable)

A1: Long - Offset to the source address

Z: Long - target address (egB. range variable)

A2: Long - offset to the destination address

N: Long - Number of Words that should be changed to Longs

Result: Long - 0

Example:

ChangeWordsToLongs (area #, 0, field #, 20000.5000)

follows:

Address: 0 1 2 3 4 5 ... 20000 20004 20,008

20012 20016 ...

Value: 11123 11123 11123 11123 11123 11123 ... 11123 11123 11,123

11123 11123

Execution time, 40,000 Words:

Original Secular = 10070 milliseconds

ProSpeed.dll = 1 millisecond

CleanUp (M)

Cleans up the internal sprite tables. Each Sprite table whose Sprite marking M and had

(apparently) has been deleted, hereby fully released.

M: Long - marking (for certain sprites)

Result: Long - 0

Each sprite of ProSpeed.dll stores its data in a table. All tables are here together

concatenated. Now, when a sprite is deleted, its table marked as deleted, but there

so long, until the last sprite was deleted. This is a good thing, should therefore still on a Sprite

be accessed, although it has already been deleted, simply nothing happens. If the complete

Table memory for the sprite completely erased, then it would otherwise be a fun fall ...

CleanUp () cleans up and deletes all the tables properly marked with M, are no longer needed.

CleanUp () should nevertheless not be carelessly used, possibly because features such as CollideMore ()

thereafter, may receive incorrect values, suchAs sprites, whose memory does not exist any more. If, however, very

have initiated many sprites and deleted again, is CleanUp () now and again a very useful and speeds up

the whole sprite thread again.

When they work in their sprites have no label, you can specify for M zero.

Oh yes, several CleanUp () should - functions are not consecutive, otherwise only the first

is executed. Namely, the function does not work immediately (of course, but immediately returns to the main program

back), but only at the appropriate place in the sprite thread. A possible solution for several CleanUp ()

Calls within a continuous loop would be:

& x = Rnd (3)

Case & x = 0: CleanUp (20)

Case & x = 1: CleanUp (114)

Case & x = 2: Cleanup (34)

ClearWith (V, A, B, N)

Deletes a part of an area (or all) with a specific value (byte format).

Inspired by the profane command

Delete with zeros can, but with all values between 0 and 255

V: Long - range variable

A: Long - Offset

B: Long - byte, should be deleted with the (0-255)

N: long - the number to delete key bytes

Result: Long - 0

Example (describes a 200,000-byte field with the byte value 128):

ClearWith (area #, 0,128,200000)

CloneFX (H)

Creates a copy of one of

copied, as well as the actual image in the array.

H: Long - one with a handle

Result: Long - Handle of the generated byte arrays.

The handle of the array must be copied later, as usual, with

Collide (H1, H2)

Tests whether just two sprites collide.

H1: Long - Sprite 1, first with the handle of a InitSprite () generated sprites

H2: Long - Sprite 2, second one with a handle InitSprite () generated sprites

Result: Long - Status of the collision or in error 0

For result, there are these two possibilities:

0 = no collision takes place the moment these two sprites or there has been a failure

1 = two sprites are just touching

This function does not work with pixel, but checks whether the areas) (width x height of the sprites are

. touch That she is working at lightning speed. But if they need a pixel-perfect collision routine, then

they take better

x & = Collide (sprite1 &, & sprite2)

CollideAll (H)

Tests whether the sprite collides with the handle H with any other sprite.

H: Long - one with a handle InitSprite () generated sprites

Result: long - 0 or handle of the sprite first found that just collided.

This function does not work with pixel, but it is a quick way to an almost complete

Collision detection. More detail (and is) just as fast

Does not times 1 millisecond to hundreds of sprites ...

Very useful with the functions

x & = CollideAll (& sprite)

CollideMore (H, B, D)

Tests whether the sprite with the handle H collision with other sprites straight.

H: Long - Handle with a generated InitSprite () sprites.

B: Long - range variable in a list of sprite handles (Longs) stands.

A: Long - the number of Sprite handles that are in Area B.

Result: Long - 0, on error or no collision, otherwise handle Sprite First encountered in the area B, which is currently colliding with H

This function works very fast, but not with pixel accuracy. That may now many sprites on a

Collision be tested without the profane would have a slow loop to be used for this purpose.

Example:

VarToLong4 (area #, 0, & sprite1, sprite2 &, & sprite3, sprite4 &)

VarToLong4 (area # 16 & sprite5, sprite6 &, & sprite7, sprite8 &)

VarToLong4 (area #, 32, sprite9 Leave &, & sprite10, 0.0) '10 Sprite handle in the field

x & = CollideMore (& sprite, area #, test 10) 'whether sprite0 & with one of these

CollideUnknown (B)

Identified in one go, all (!) Sprite to sprite collision that takes place at the moment!

B: long - pointer to an area that can absorb the collision data

Results: Long - the number of found Sprite collisions.

Long demanded, and now it finally is! A complete solution for all sprite collisions, the straight

. held

CollideUnknown () works within a millisecond, and lists all conflicts in the region B.

Together with

Two each sprite handle (yes, a collision takes two sprites) are as LongInt

write a row in the range B.

Offset significance

0 1. Handle by Sprite Collision 1

4 2. Handle by Sprite Collision 1

8 1. Handle by Sprite Collision 2

12 2. Handle by Sprite Collision 2

16 1. Handle by Sprite Collision 3

20 2. Handle by Sprite Collision 3

...

Small sample program to evaluate these collisions:

Clear Kollis #

x & = CollideUnknown (# parcels)

If x &

& y = 0

Whileloop x &

a & = Long (parcels #, y &)

b & = Long (parcels #, y & +4)

Print "No Collision" + Str $ (x &)

Print "1 = sprite handle," + Str $ (A &)

Print "Sprite Handle 2 =" + Str $ (b &)

'*** This could now according to certain collisions

'*** To respond (forVia Mark B. Sprite)

y = y & & +8

Wend

EndIf

It should be mentioned, are filtered out of the double collision ProSpeed already, that is

Thus, the present two of the same handle twice in different order.

That does not mean that prejudice, if more than two sprites, they are not listed!

Here's an example - adopted there were three sprites and sprite, all three would be another

. touch Then the content of B would look like this:

0 Handle by Sprite 1 \

) - Collision 1

4 Handle by Sprite 2 /

8 Handle by Sprite 1 \

) - Collision 2

12 Handle by Sprite 3 /

16 Handle by Sprite 2 \

) - Collision 3

20 Handle by Sprite 3 /

CollideUnknown () returns in this case a value of 3 (three collisions).

Collision (H1, H2, X, Y)

Tests whether just two sprites collide.

H1: Long - Sprite 1, first one with a handle InitSprite () generated sprites

H2: long - Sprite 2, second one with a handle InitSprite () generated sprites

X: How long - X size of the pixel sampling

Y: Long - Y extending the pixel sampling

Result: Long - Status of the collision or in error 0

For this result, there are two possibilities:

0 = no collision takes place at the moment these two sprites or there has been a failure

1 = two sprites are just touching

This feature has been completely rebuilt for ProSpeed V2.1 and is now working with other technology. Two

Parameters have been added to herabzusetzten the duration of this function. So far Collision () was very

slowly, which lay on the scan and pixel-perfect, with 0 / 0 in the parameters X and Y is the function

still just as slow.

X and Y say they are number of pixels in the sensing Collisions always skipped, so must

far fewer pixels are examined. A call to Collision (sprite1 &, & sprite2, 4.4) forB. goes very fast

, and is still very safe in the collision detection. To the best values for their two sprites

to figure out they should just play around a bit.

A restriction on certain video modes are now available for Collision anymore.

x & = Collision (sprite1 &, sprite2 &, 4,4)

Colorfill (A, F)

Colors, an effect byte-array in a particular color.

A: Long - one with a goal-Handle

Byte arrays

Q: Long - RGB color value

Paint a very simple function is a ByteArray quickly.

Colorfill (array &, RGB (126,34,220))

ColorFillImage (V, R, X1, Y1, X2, Y2)

Fill a rectangular area of a bitmap with color in V R.

V: Long - HDC

R: Long - RGB color value.

X1: Long - Left offset, in pixels, in which begins the filling.

Y1: Long - Upper offset in pixel on which begins the filling.

X2: Long - Right-hand offset in pixel, of termination of the filling.

Y2: Long - lower offset in pixels, of termination of the filling.

Score: 0

Example:

ColorFillImage (HDC &, RGB (255,0,0), 0,0,% maxx, maxy%) 'Fills the HDC completely red.

Sometimes you must have a HDC fill with a specific color. This is now without a lot of

Expenditure. But ColorFillImage () is still so flexible that even an arbitrary

rectangular area can be filled.

ColorMove (F, X, Y, B1, B2, S)

Mixes two different images into one, unlike

transparent mixed, but it will only approximate the colors of both images. This function is

much faster than SEMITRANS (), and it can be displayed with a trick images

Not only are rectangular, sprites, for, for example,

Q: Long - Handle of the target bitmap (HDC) or 0

X: Long - X offset to screen

Y: long - Y offset to the screen

B1: Long - First one with a handle

B2: long - produced with the handle of a second PngToFX (), InitFX () or CreateFX () byte array (2. source bitmap)

S: long - step of alignment.

Result: Long - 0

The colors of the graphic with the increment S B2 are increasingly closer to the colors of the graph B1.

The byte data of B2 are changed by this. If it the background along with an image

want to combine, they must work with a corresponding copy of the background, which for

B1 or B2 is used.

X and Y specify the upper left corner where they have placed both images. The size of the display

Rectangle is derived from the size of the bitmap that is specified in InitFX () / CreateFX (). The size

of B1 and B2, but must always be the same size!

For F one of profane can either be specified or a bitmap, with LoadFileImage () /

CreateImage () was created. Is passed, however, for F 0, the function will be executed but

not brought to the screen.

ColorMove () and is super fast, but uses an 400 MHz computer, even with large screens

in real time. Generally applies: The smaller the area, the faster this function works.

Before the function can be used, must be a preparation with InitFX () have taken place.

The data in the byte array B1 are not changed by calling this function already from B2.

The larger the step size S is, the faster it will appear. Here, values are from 1-255.

Example:

A sprite appears quite soft in the existing background image.

fxhandle1 & CreateExtImage = (% hdc, 80.80) 'Handle 1: Creating empty bitmap

Paint Image (fxhandle1 &, 0,0,80,80,% HDC, 0,0,0) 'Content of the Profanfensters to handle 1

$ name = "picture.bmp"

fxhandle2 & LoadFileImage = (addr ($ name)) 'Handle 2: Sprite invite suchB. 80x80 size

Paint Image (fxhandle1 &, 0,0,80,80, fxhandle2 &, 0,0, -1) 'in the Sprite

Paint Image (fxhandle2 &, 0,0,80,80,% HDC, 0,0,0) 'Content of the Profanfensters to Handle 2

bytearray1 & = generate InitFX (fxhandle1 &) 'byte array to handle 1

bytearray2 & = generate InitFX (fxhandle2 &) 'byte array to Handle 2

WhileLoop 256

ColorMove (% HDC, 0.0, & bytearray1, bytearray2 &, 1) 'The sprite is displayed in 256 steps in the' background image

Wend

FreeFX (bytearray1 &) 'byte array 1 unlock

FreeFX (bytearray2 &) 'byte array 2 unlock

FreeImage (fxhandle1 &) 'Handle 1 unlock

FreeImage (fxhandle2 &) 'Handle 2 unlock

CompareBytes (B1, B2, A, D)

A compares the two bytes of memory areas B1 and B2 for equality and Discrepancies.

B1: Long - 1 area variable

B2: Long - range variable 2

A: Long - Number of bytes to be reviewed

T: Long - tolerance for each byte comparison

Result: Long - 0 for complete compliance, otherwise number of different bytes.

Often a necessary function, especially suitable to compare texts or bitmaps, and as always very fast.

T will normally be zero. You can also specify a tolerance with. If the two bytes of

the two areas are compared, and the difference between the two is not larger than the

Tolerance value, then the comparison is positive, the two byte values can therefore be considered equal. At

Tolerant of 10 for aAs were the two numbers 201 and 208 than it was rated the same.

Examples:

(1. Compares 80,000 bytes of data from two areas, with no tolerance)

(2. Compares two images (jpg and bmp, the same motif with one another), 4 x with different tolerances (0, 10, 50, 100)).

x & = CompareBytes (area1 # Range2 #, 80000.0) 'Example 1

Print "number of different bytes:" + Str $ (x &)

$ text = 'Picture' example 2

LoadFileImage & pic1 = (addr ($ text))

$ text = "Picture.jpg"

LoadFileImage & pic2 = (addr ($ text))

array1 = InitFX & (& pic1)

array2 = & InitFX (pic2 &)

bytes & = Long (& array1, 20), size of the images in bytes (both) is equal

x & = Long (& array1, 40); pointer to byte array of picture 1

y & = Long (& array2, 40); pointer to byte array of picture 2

CompareBytes = z & (x & y &, & bytes, 0)

Print "number of different color pixels (of" + Str $ (bytes &)+"): "+ Str $ (z &)

CompareBytes = z & (x & y &, & bytes, 10)

Print "Number of different color pixels (of" + Str $ (bytes &)+"): "+ Str $ (z &)

CompareBytes & z = (x & y &, & bytes, 50)

Print "number of different color pixels (of" + Str $ (bytes &)+"): "+ Str $ (z &)

CompareBytes & z = (x & y &, & bytes, 100)

Print "number of different color pixels (of" + Str $ (bytes &)+"): "+ Str $ (z &)

FreeFX (array1 &)

FreeFX (& array2)

FreeImage (pic1 &)

FreeImage (pic2 &)

Compute (B, A, F ,+,-,*,/, S)

Applying simple arithmetic operations on all or some of the long integer (optional integer or bytes) in one area.

B: Long - range variable (memory address)

A. Long - Number of bytes in B, which will be re-calculated with Compute ()

Q: Long - flag, which number system is used: 1 = byte / 2 = Integer / 4 = LongInt

+: Long - This value is added to each number in the field

-: Long - This value is subtracted to each digit in the range

*: Long - This value is multiplied by every number in the range

/: Long - Each number in the field is divided with this value (decimal digits are truncated)

S: Long - After each number as many bytes skip, usually 0

Results: Long - 0

With Compute () lot numbers can simultaneously adds, subtracts, multiplies, and / or be divided.

This can be set (for F), whether the numbers in the range B bytes, integers or LongInt's supposed to be. A 1

ie, all numbers are treated as bytes. At 2, all numbers are treated as an integer, as LongInteger at 4.

In S can be specified whether each number in the field should be recalculated after each number, or whether

a certain number of bytes to be skipped.

+, -, * And / can all be used simultaneously or individually, or otherwise combined, the

Order, with all four should be expected, is always Multiply: - subtract divide - add -.

If it is determined in F, will use the byte or integer (1 or 2), must be noted that

Secular bytes and always as an unsigned integer in areas, handle only with positive numbers

calculated. Negative numbers so obtained therefore incorrect values. At long integer that is not as if they are

always signed deals with negative numbers, and also provide a correct result.

Bytes only within the numbers 0 to - operate 255, integer numbers in the 0 - 65535th Long

Integer can expect numbers from -2,147,483,648 to 2,147,483,647.

Example 1:

$ text = "10,20,30,40"

SetBytes (area #, 0, addr ($ text))

Compute (area #, # 4,1,0,0,0,10,0) 'Results of the first four bytes in the field: 1, 2, 3, 4 (all bytes / 10)

Example 2:

$ text = "10,20,30,40"

SetWords (area #, 0, addr ($ text))

Compute (domain # # 8,2,0,0,10,0,0) 'Results of the first four integers in the field: 100, 200, 300, 400 (all integer * 10)

Example 3:

$ text = "10,20,30,40"

SetLongs (area #, 0, addr ($ text))

Compute (area #, # 16,4,11,22,0,0,0) 'Results of the first four LongInt Area: -1, 9, 19, 29 (all LongInt + 11 to 22)

Example 4:

$ text = "10,10,20,20,30,30,40,40"

Clear area #

SetLongs (area #, 0, addr ($ text))

Compute (area #, # 32,4,0,0,123,321,4) 'Results of the first eight LongInt Area: 3, 10, 7, 20, 11, 30, 15, 40

'(every second LongInt * 123 / 321)

CopyFX (F, X, Y, B)

Manually copy of a byte array to the on-screen (or portions thereof).

Q: Long - Handle of the target bitmap (HDC) generated)

X: Long - X Offset in F

Y: Long - Y offset in F

B: Long - one with a handle

Result: Long - 0

= array & InitFX (exhdc &) 'Handle (byte array) to create a bitmap

FlipX (% HDC, 0.0, array &)

FreeFX (array &) 'later release

= array & InitFX (exhdc &)

FlipX (0,0,0, array &)

CopyFX (% HDC, 0.0, array &)

FreeFX (array &)

CopyMemory (Q, A1, Z, A2, B)

Copies the contents of a memory block to another location somewhere in memory.

The command works from left to right,. It should only be used as long as no overlap

occurs between source and target range.

Q: Long - the source address (egB. range variable)

A1: Long - Offset to the source address

Z: Long - target address (egB. range variable)

A2: Long - offset to the destination address

B: Long - Number of bytes that should be copied

Results: Long - 0

Examples:

CopyMemory (Table 1 #, 0, Table2 #, 0.10000)

CopyMemory (Table1 #, 4000, Table1 # 3000.1000)

Execution time, 40000 bytes:

Original Secular = 4850 milliseconds (with copy WhileLoop-loop)

ProSpeed.dll = <1 millisecond

CopyMemoryFromBack (Q, A1, Z, A2, B)

Functional description, see

Both commands have an equivalent effect, and syntax working internally but different.

CopyMemoryFromBack works from right to left. This method can also overlap

be the source of the area and target area properly copied.

CopyMemory CopyMemoryFromBack are equal and fast in their execution.

First, an example of CopyMemory:

CopyMemory (Table #, 0, Table #, 1.8)

8 bytes will be shifted within a range of 1 byte to the right. The bytes are

copied from left to right. CopyMemory is wrong here, but write values.

------------------------

From this sequence of bytes 0 -> 1 -> 2 -> 3 -> 4 -> 5 -> 6 -> 7 -> 8 9 10 11 ...

is 0 0 0 0 0 0 0 0 0 9 10 11 ...

Byte 0 is copied to byte 1, then byte 1 (now the value of byte 0 will have) copied to bytes 2,

Byte 2 to byte 3, etc.

Now the same command CopyMemoryFromBack as:

CopyMemoryFromBack (table #, 0, table 1.8)

This time, however, the memory area is copied from right to left.

"

From this sequence of bytes 0 -> 1 -> 2 -> 3 -> 4 - Over 5 -> 6 -> 7 -> 8 9 ... 10 11

will be 0 0 1 2 3 4 5 6 7 9 10 11 ...

Byte 7 byte is copied to 8, then byte 6 to byte 7, byte 6 to byte 5, etc.

CopyMemoryFromBack so it works correctly.

The other way around would work at the command of the command correctly and CopyMemory

CopyMemoryFromBack would write incorrect values in the memory:

CopyMemory (Table # 1, Table 0.8)

8 bytes this time should be moved within a range of 1 byte to the left.

CopySprite (H)

Copy the sprite with the handle H with identical values.

H: Long - one with a handle

Result: Long - on error 0, otherwise handle the new sprites

This function makes a sprite two.

Example:

new & (= old & CopySprite)

CountAllSprites ()

Counts how many tables exist Sprite. Counting all the sprites so far are also deleted!

Result: Long - Number Sprite Tables

Count bytes (V, A, N, B)

Testing a part of an area (or all) to a specified byte, and reports how many bytes in

the area occurs.

V: range variable

A: Long - Offset Address

N: Long - Number crawler bytes

B: Long - to look up Byte

Results: Long - Number of bytes found

Example:

(Tests, how many times the byte 128 in a 40,000-byte field.

& # x = range (Count bytes, 0,40000,128)

Print "Number of bytes =" + Str $ (x &)

Number of bytes = 5867

First count bytes (V, A, N, B)

Testing a part of an area (or all) to a specified byte, and reports how many bytes

occurs first in the area until another byte is found. Useful forFor example, to identify,

How many spaces initially appear in a string before the regular text is reached.

V: range variable

A: Long - Offset Address

N: Long - Number crawler bytes

B: Long - to look up Byte

Results: Long - position at which occurs a different byte than B

Example:

'Code expires Secular 7, have to work with Profanversionen previous range variables ...

$ string = "Hello"

x & count = First Bytes (Addr (string), 0, Len (string), 32) 'Chr $ (32) = blanks

Print "Number of leading spaces:" + Str $ (x &)

Number of leading spaces: 12

Count joystick buttons (N)

Determines the number buttons, and available on the attached joystick N.

N: Long - the number of joysticks, 1 or 2

Result: Long - the number of available joystick buttons in error 0

x & count = joystick buttons (1)

Long Count (V, A, N, L)

Testing a part of an area (or all) to a specific longword (long) and reports how

often the longword in the area occurs.

Please note that in an area of suchDimensioned as with 10000, was only 2500 Longs

may occur (1 Long = 4 bytes).

V: range variable

A: Long - Offset Address

N: Long - Number crawler-Long Words

L: Long - to look up longword

Results: Long - Long Number of found Words

Example (Secular 7):

(Tests, how many times the LongInt 178,064 in 40,000-byte field.

& # x = range (Count bytes 0,10000,178064)

Print "number of integer =" + Str $ (x &)

Number of Integer = 47

Count sprites ()

Counts how many sprites are redrawn are currently / running.

Result: Long - Number of sprites

Count strings (V, A, N, S, L)

Testing a part of an area (or all) on the contents of a string and report how often the

String in the field occurs.

V: range variable

A: Long - Offset Address

N: Long - Number crawler-byte (length of the area, the ground is searched)

S: string (or area) that contains the search string

L: Long - Length of the search string in bytes

Results: Long - the number of found strings

Example (Secular 7):

(Tests, as often happens, the string "Hello" in a 80,000-byte field.

$ text = "Hello"

x & count = string (domain #, 0.80000, addr ($ text), Len (text $))

Print Chr $ (34) + text $ + Chr $ (34) + "was" + Str $ (x &) + "x in the area before."

"Hello" x 61 came before in the area.

CountWords (V, A, N, W)

Testing a part of an area (or all) on a particular word and report how often the Word

occurs in the area.

Please note that in an area of suchDimensioned as with 10000, was only 5,000 Words

may occur (1 Word = 2 bytes).

V: range variable

A: Long - Offset Address

N: Long - Number crawler Words

W: Long - to look up word

Results: Long - Number of found Words

Example (Secular 7):

(Tests, how often the Integer / Word 4064 appears in a 40,000-byte field.

& # x = range (Count bytes 0,20000,4064)

Print "Number Integer =" + Str $ (x &)

Number of Integer = 644

AddWindowStyle (W, S, F)

(To enable one or more) Windows Extended Window flags and flags, and thus changes the appearance

a window.

Watts: Long - Handle of a window, or (forB. HWnd%) or a control (for, for example,

Box)

S: Long - level (s) for Window Style (s), or Extended Window Style (s)

Q: Long - flag, which style is used: 0 = Window-Style / 1 = Extended

Window Style

Score: 0

This looks like a window can be changed, which is already open. AddWindowStyle () adds

this, the specified Style with S added. This can have a combination of multiple window

His styles. However, the standard Windows styles may not with the extended window styles

be combined! If they want more one (or) extended window style (s) to add, then

must be specified for F is 1, for standard Windows styles a 0

Examples:

(1. Adds Profanfenster a horizontal and vertical scroller added)

CreateFX (B, H)

Creates a byte array structure manually.

B: Long - Width of the imaginary image

H: Long - the amount of the imaginary image

Result: Long - Handle a byte array structure, in error 0

A byte-array structure is created. The graphic data (pixel data), so the actual byte array) is filled with 0 values (black image.

For further explanations under

CreateFX (1024.768)

CreateImage (V, W, H)

Creates an empty bitmap.

V: Long - Secular variable% HDC

B: Long - Width of the new bitmap

H: Long - the amount of the new bitmap

Results: Long - Held handle of a memory device context (in-memory image data structure, HDC).

On failure 0

Example:

ExternHDC & CreateImage = (% HDC, 100.40) 'Creates an empty, 100 x 40 pixel bitmap' in memory

The bitmap will be held so long in the memory until it through

no later than the end of the program carried out in order to provide the resources free again.

Currently can be simultaneously held in memory up to 32 external bitmaps, nor to whom the

bit is the sign for me please.

This function should only be called when the profane has already opened a window.

Crypt (B, A, S, L)

Encrypted data in an area with a password of any length. In the same call twice

are the original data restored.

B: long - a range variable that stores the data

A: long - number of bytes to encrypt

S: Long - pointer) on a string (or area that is stored in the password

L: Long - length of the password

Result: Long - 0

A super-fast and relatively secure data encryption to password-based XOR.

Example:

$ name = "Datenfile.dat"

x & = (FileSize $ name)

ReadFileFast (addr ($ name), area #, 0, invite x &) 'file / data in a range variable

$ password = "CryptMe" 'password' is CryptMe "

Crypt encrypt (area #, & x, addr ($ password), len ($ password)) 'Data from the field

$ name = "Datenfile_crypted.dat" 'This could be the encrypted file back

WriteFileFast (addr ($ name), area #, 0, & stored x) '...

Crypt (area #, will & x, addr ($ password), len ($ password)) '... or returned to its original condition'

Curve (H, SX, SY, CX, CY, EX, EY)

Draws a curve in the bitmap of any HDC's.

H: Long - HDC

SX: long - starting point, X-axis

SY: Long - the starting point, Y-axis

CX: Long - Control Point (center), X-axis

CY: Long - Control Point (center) Y-Axis

EX: Long - end-point, X-axis

EY: Long - end-point, Y-axis

Result: 0

A function to draw an arbitrary curve. The color of the curve with the usual

Graphics commands set. From the starting point of the curve is the control point is up to this

Rounded point and then continues to the end point. H can be any HDC, HDC also%.

Curve (% hdc, 50,50,400,300,100,200)

Darken (F, X, Y, B, S)

Darkening of the screen (or portions thereof) to a black surface.

X: Long - X offset to the screen

Y: Long - Y offset to the screen

B: Long - one with a handle

S: Long - step of darkening

Result: Long - 0

The screen is obscured by S stages. S may here from 1 to 255th The current graphics mode is

for this function does not matter. Intern is expected with 24 bits.

X and Y specify the upper left corner, is obscured from the on-screen. The size of the

blackout zone results from the magnitude of the bitmap that is specified in InitFX () / CreateFX ().

For F one of profane can either be specified or a bitmap, with LoadFileImage () /

CreateImage () was created. If passed, but for R 0, the function will be executed but

not brought to the screen.

Darken () is pretty fast and works in real time. Larger screens (egB. 1024x768) should be based on

slow computers, but not in 1-step increments shall be darkened. From a 600 processor should

But the speed of this range.

Generally, the smaller the area, the faster it darkens.

Before Darken () can be used, must be a InitFX preparation with () have taken place.

The data in the byte array B are changed by calling this function ..

Example:

A screen will gradually darken:

= array & InitFX (exhdc &) 'Handle (byte array) to create a bitmap

WhileLoop 256

     Darken (% HDC, 0,0, & array, 1)

EndWhile

FreeFX (array &) 'later release

Data Bytes (S)

An implementation of the Basic DATA command for the profane. "Data Bytes ()" is also available as a procedure "Data".

S: Address of a string with input instructions

Results: Long - 0

Secular does not know the DATA command. Practically, however, it would be a feature to a memory area

Assign (range) data.

ProSpeed does this have long

one step further.

First, is determined by Datames (), should have access to what area of data bytes / data next.

Datames () sets this automatically positioning on the first byte of the target area (

Datames (domain #)

Data 250,128,23,56,251,83,90,12,7,252,253,0,26,124,78,78,43,202 "

Data 1,254,59,255,77,200,201,45,202,203,204,205,206,207,56,23,78 "

Data "228.23"

Datames (memory #)

Data 206,56,23,78 "

Data 250,124,78,78 "

Data 77,200,201,45 "

(This source code uses the procedure "Data". If they file in their program

ProSpeed_Funktionen.inc

With this source would be the first 37 bytes of the area described area # ", then the first

12 bytes of the area "stored #".

Data Bytes () / data can be used very well for images or other data directly into the

Source include (in order to incorporate more compact data, please use

The string S can contain only numbers, commas, spaces, and Zodiac, variables are not

allowed. ProSpeed converts this string into individual bytes and writes them into the area. The

Zodiac is a dummy character. More here at

In ProSpeed package contains a program

easily to any file in data lines can be converted. The so-generated lines can

be copied directly into the Secular-source, or as Inc-file are stored.

An illustrative example is the Data Generator Source itself. In any case reinschauen times.

Datames (B)

Sets a new area for data bytes (). The next data bytes () then takes over to this area from position 0.

B: New Area for the next data byte () to determine and byte offset set to 0

Results: Long - 0

More info, see

DataPos (P)

Sets a new position for Data Bytes (). The next Data Bytes () then accesses from that position on the field.

P: Position (offset) of the next data bytes ()

Results: Long - 0

More info, see

DeInitPixelEffects ()

Ends the pixel effects.

Result: Long - 0

DeInitPixelEffects () terminates the thread again, with

Be done before the end of the program to release all the memory it has.

DeleteAllSprites ()

Removes all sprites from the screen.

Result: Long - 0

If at the end of a program are always used to make sure that all sprites

been deleted. Otherwise it when exiting the program come to a profane message.

DeleteAllXSprites (X)

Removes all sprites from the screen, which are currently on-screen position X.

X: Long - display position in the X-axis

Result: Long - number of deleted sprites.

Can be very useful. Certain types of sprites can be deleted without knowing its sprite handle.

Sprites from the screen, etc. running

DeleteAllXSprites (-40)

DeleteAllYSprites (Y)

Removes all sprites from the screen, which is currently underway to screen Y position.

Y: Long - Display position in the y-axis

Result: long - number of deleted sprites.

Can be very useful. Certain types of sprites can be erased without knowing its sprite handle.

Sprites from the screen, etc. running

DeleteAllYSprites (-40)

DeleteSprite (H)

Deletes the sprite with the handle H.

H: Long - one with a handle InitSprite () generated sprites

Result: long - 0

Deletes the sprite from the screen. H shall henceforth no longer be used.

DeleteSprite (& sprite)

DeleteSpritesIfAnimReady ()

Delete all completed sprites from the screen, the animation was in mode 1.

Result: Long - number of deleted sprites.

Very useful in connection with

Optimal for suchUsed as explosions, explosion sprite is removed when the animation has been run.

DeleteSpritesMark (Z)

Removes all sprites from the screen, which were labeled with the number Z.

Z: Long - the number with which the sprite by

Result: Long - the number of deleted sprites.

Very useful in connection with

DeleteSpritesMark (111),

DeleteTags (Q, A, Z, C1, C2, F)

Removed, or collect or store text passages that are located within two days mark.

Q: Long - pointer to a storage area (or string) with the source data

A: Long - Number of bytes to be processed in Q

Z: Long - pointer to a storage area (or string), be written in the target data

C1: Long - ANSI code of the start bytes

C2: long - ANSI code of Endbytes

Q: Long - Flags

Results: Long - Number of characters that were generated in Z.

Quite a versatile function, which can decrease the workload.

For example, could hereby Html tags are removed that are in angle brackets (<and>), or

Comments are deleted from source code ( 'and ANSI code 10), etc. Certainly there are still

all sorts of custom applications ...

Q and Z are pointers to memory or strings.

C1 and C2 can be values from 0 to 255, not higher! Both are ANSI code values. You should always

get different values.

Flags (F), there are now 2 (combined):

0 = no flag.

1 = Not the tags are removed, but everything else is removed, which

not between C1 and C2 (ie without tags are located).

2 = The tag characters C1 and C2 are the removal / collection not affected

The result is the number of characters / bytes that were generated in the target area Z. In addition, as is

End identifier inserted a null character!

For example, see Source

DePack (Q, Z, P)

Decompressed (unzipped) a data area again, with

Q: long - pointer to a source (or string pointer to an area) with the packed data.

Z: Long - pointer to the destination are stored in the extracted data

(Z = Q may not be, a second storage area is needed).

P: Long - pointer to a string / field that contains a password, or 0 (no password is used)

Result: Long - Number unpacked bytes. In Error = 0

The technology that lies behind DePack (), does not come from my pen. There is here the aPLib of

Joergen Ibsen uses a library that uses an LZ compressing technology, read more

below.

If they use the in ProSpeed.dll freeware program, it may DePack () / free aPLib

used, but in kommerizieller shareware programs and software they need aPLib

The aPLib license obtained for $ 29 (Company for $ 95) at Joergen Ibsen (

Courtesy. aPLib, copyright © 1998-2002 by Jørgen Ibsen.

Data extracted again with

It is not necessary to specify the number of bytes packed somewhere, because this information into the packed

Data has been integrated.

To find out how many bytes the extracted data show later, must

DePack () works very quickly.

Example (for loading, unpacking and decryption, also see example of pack ()):

$ text = "File Name"

(bytes FileSize = & $ text)

Dim range #, & bytes

ReadFileFast (addr ($ text), area #, 0, & bytes)

(neubytes & area = GetOriginalSize #)

Dim target area #, neubytes &

Print "compressed data =" + Str $ (& bytes) + "bytes."

Print "Calculated to extracting data =" + Str $ (neubytes &) + "bytes."

$ text = "password"

x & = DePack (area #, # target area, addr ($ text))

Print

Print "data = unpack" + Str $ (x &) + "bytes."

Compressed data = 5408 bytes.

Calculated, to decompress data = 48,030 bytes.

Data extracted = 48,030 bytes ..

DownloadHttpFile (U, D)

Downloads a file from the Internet onto your hard drive. See also

U: string (or area), which contains the name of the HTTP file

D: string (or area) that contains the filename of the file to be written

Result: Long - 0, 0 on failure " '

IfNot DownloadHttpFile ( "http://frabbing.de/bg.gif", "c: / test.txt")

Print "File has been generated."

Else

Print "Download failed!"

EndIf

DSoundDeInit ()

Deinitializing DirectSound again and releases the memory. After this function DSound not allowed -

Function be called.

Result: Long - 0

DSoundGetInterfaces (S)

This feature makes ProSpeed's DirectSound functions compatible with King Sebastian DirectSound profane procedures.

S: Long - pointer to a variable that receives the interface pointer of the primary buffer.

Result: Long - IDirectSound interface pointer of the object.

Sebastian King DSInitFromProSpeed handler () uses DSoundGetInterfaces () to Dll and profane

Template to make them compatible. So they can combine both. Only for Professionals, and the ProSpeed

Sebastian's wish to combine templates.

Example:

IDirectSound & DSoundGetInterfaces = (Addr (DSBPrimary &))

DSoundGetNextBuffer (A)

This function returns a single buffer from a buffer array.

A. Long - pointer to a buffer array, with

Result: Long - pointer to the buffer, which will be played next with DSoundPlay ()

The result of this function is one of the 15 buffer from a buffer array, namely the buffers, as

Next with

Sounds are altered before the sound is played.

Please note, the play buffer and a pointer to a storage area, whereas buffer and a pointer to a

Array storage areas is ...

play buffer & = (& buffer DSoundGetNextBuffer)

DSoundGetStatus (B)

This function determines the status of a sound game.

B: Long - pointer to a buffer, by

Result: long - Status

The result returns the status.

If Bit 0 (value 1) set, the sound / buffer is playing, otherwise he is already finished.

If bit 2 (value 4) is set, then the sound as loop (infinite) is issued.

status & = (DSoundGetStatus buffer & play)

DSoundInit (F)

Initialize DirectSound, a part of DirectX. So to use the functions of DSound ProSpeed.dll to

DirectX must be installed.

DSoundInit () must be called before using any DSound other features.

Q: long - Handle of the Secular window (hwnd%)

Result: Long - 0 = OK / not 0 = failure.

If DSoundInit () is called, must have a window (F) be open.

DSoundInit (hwnd%)

DSoundLoad (S)

Load a Wave file to play later.

P: long - pointer of a string with the name of a wave file

Result: Long - 0 = Error / else a pointer to a buffer array (important for

A wav-file is loaded and stored in a buffer array.

Actually be in the buffer array created 15 copies of the sound, plus a counter. These 15

Copies of the same evidence, however, DirectSound internal memory, so that no memory is wasted.

Why 15 copies? Each copy can be played only once at a time. But 15 when we

Copies have, also can sound like 15 times one and will be played simultaneously, and that ought to

Every game rich, what we create ...

$ text = "test.wav"

buffer = & DSoundLoad (addr ($ text))

DSoundLoadMemory (B, A)

Load a wave file from memory for later playback.

B: range variable

A: Long - Number of bytes in the field

Result: Long - 0 = Error / else a pointer to a buffer array (important for

A wav file is loaded from a storage area and stored in a buffer array.

Actually be in the buffer array created 15 copies of the sound, plus a counter. These 15

Copies of internal evidence, however, the same DirectSound memory, so that no memory is wasted.

Why 15 copies? Each copy can be played only once at the same time. If we are but 15

Copies have also 15 times can sound like one and be played simultaneously, and that ought to

Every game rich, what we create ...

(This function has no extra-offset parameter, as in fact functions in many normal range.

Whether it is written now, a comma or a plus sign is eigenlich matter, as the following demo shows

which invites four samples from a storage area.)

buffer1 & = DSoundLoadMemory (area # 8200)

buffer2 & = DSoundLoadMemory (domain # +8200.16003)

buffer3 & = DSoundLoadMemory (domain # +24203.4004)

buffer4 & = DSoundLoadMemory (domain # +28207.22401)

DSoundLoadResource (H, S)

Load a wave file from a resource file for later playback. A resource file, a dll

his or Exeprogramm (forAs our own) that is linked together with data.

H: Long - hInstance a Exedatei or the handle from a loaded dll.

S: Long - the number of the resource or string with the name of the resource

Result: Long - 0 = Error / else a pointer to a buffer array (important for

A wav file is loaded as a resource and stored in a buffer array.

Actually be in the buffer array created 15 copies of the sound, plus a counter. These 15

Copies of internal evidence, however, the same DirectSound memory, so that no memory is wasted.

Why 15 copies? Each copy can be played only once at the same time. But 15 when we

Copies have also 15 times can sound like one and be played simultaneously, and that ought to

Every game rich, what we create ...

For S is a number (long) or can a specify string (resource name). It can even be a number

be specified in the string, then the first character in the string must be a # and the rest is as a figure

interpreted, suchB. $ text = "# 100". S for a string is specified, then he must at least 3 characters

contain names with fewer characters are not allowed.

For H is a DLL or the hInstance of Exeprogramm can be specified, including a foreign

Exeprogramm, which contains resources that can be specified, if the hInstance of this program

was determined.

Note: Wave files in resources must be as resource type "WAVE" saved!

Examples:

1.)

DSoundInit (hwnd%)

dll & usedll = ( "Resource.dll")

$ text = "Sound1"

buffer1 & DSoundLoadResource = (dll &, addr ($ text))

2.)

buffer1 & DSoundLoadResource = (% hInstance, 100)

DSoundPlay (A, L)

This feature plays a sound that was loaded with DSoundLoad ().

A: Long - pointer to a buffer array, with

Play L: Long - flag for loop () into a loop. 0 = no loop / 1 = Loop

Result: Long - pointer to the playing buffer.

The result of this function is one of the 15 buffer from a buffer array, namely the buffer, the

about to be played. This value can be queried by DSoundGetNextBuffer (), without

play the sound.

Please note, the play buffer and a pointer to a storage area, whereas buffer and a pointer to a

Array of storage areas is ...

play buffer = & DSoundPlay (& buffer, 0)

DSoundSetGlobalPan (P)

This function changes the panning of all sounds the same.

P: Long - panning, -10000 = left / 10000 = far right.

Result: Long - 0

DSoundStop (5000)

DSoundSetGlobalVolume (V)

This function changes the volume of all sounds the same.

V: Long - volume, -10000 = very low / 0 = very loud.

Result: Long - 0

DSoundStop (-575)

DSoundSetPan (B, P)

This function changes the panning of a sound.

W: Long - pointer to a buffer, by

DSoundGetNextBuffer ()

P: Long - panning, -10000 = left / 10000 = far right.

Result: Long - 0

This function changes the panning of the sound in the buffer B. The values for P ranging from -10000 (quite

left) to 10000 (extreme right). A value of 0 stands) for a uniform distribution (in the middle.

DSoundSetPan (play & buffer, 5,000)

DSoundSetVolume (B, V)

This feature changes the loudness of a sound.

B: Long - pointer to a buffer, by

DSoundGetNextBuffer ()

V: Long - volume, -10000 = softly / 0 = very loud.

Result: Long - 0

This function changes the volume of the sound in the buffer B. The values for V ranging from -10000 to 0

DSoundSetVolume (play & buffer, -575)

DSoundStop (B)

This will stop a sound that is currently playing.

B: Long - pointer to a buffer, by

DSoundGetNextBuffer ()

Result: Long - 0

DSoundStop (play & buffer)

DSoundUnLoad (A)

This function returns an array buffer clear again, that was created with DSoundLoad ().

A: Long - pointer to a buffer array, with

Result: Long - 0

The copies of the sound and the sound itself be freed.

DSoundUnLoad (buffer &)

Create your own graphical effects:

Here is a description how to get a ByteArray - created with

Thus, a byte array is nothing more than an image, but this is completely editable in memory.

But you should know exactly what to do, because an accidental fall into the wrong letter

Storage areas can cause considerable damage.

That is why I have spared me so far, include this information in the manual. But since lately

more and more users use the ProSpeed.dll not only profane but also himself Dll's Profile

or faster programming languages (suchB. PureBasic) use and ProSpeed's graphical effects

want to use, I have added this chapter added.

Secular itself is too slow to be able to properly own graphical effects.

InitFX () and CreateFX () pass a pointer. He points to an original Windows structure

(BITMAPINFOHEADER). This structure was, however, of ProSpeed a Long-Int (offset added 40).

Here are the offsets:

0 LONG biSize

4 LONG biWidth, width of the image

8 Long biHeight, height of the image

12 WORD biPlanes, always 1

14 WORDS biBitCount in ProSpeed byte array is always 24 (bit)

16 long biCompression always BI_RGB

20 Long biSizeImage, size of the byte array in bytes

24 Long biXPelsPerMeter

28 LONG biYPelsPerMeter

32 long biClrUsed

36 Long biClrImportant

40 Long pointer to the memory of the byte array

The values of the structure may Secular (accessed from 7) with @ Long ..

Most interesting, of course, to offset long-Int 40th Here are a pointer to the actual image data.

In earlier versions of the ProSpeed.dll graphic was turned on its head. From version 3.0 does not

more, and the bitmap into a byte array is stored from top left to bottom right.

3 bytes per pixel are required (24-bit), a blue value, a green value and a red value (in this

Order BGR, each one byte). If the width of the image is not smooth in the byte array is divisible by four,

adds additional padding bytes into Windows, a array of bytes that the manipulation of graphics data much

complicated and slowed by additional queries. So ask all the graphical effects of the

ProSpeed.dll an image whose width is smoothly divisible by four!

After you've manipulated the ByteArray, you can CopyFX with it () to bring to the screen.

Information for other programming

If irgenwo written by areas (area #), a vulgar memory area is meant as

for heAs with the API GlobalAlloc () can be generated. As a parameter must be a pointer to the

Storage area will be returned.

Examine (Z)

Determine if a string contains a number or text.

Z: Long - pointer to a string

Results: Long - 0 = number / 1 = text

(A string must end with a null character is always string of profane) is analyzed. Does the

String only contain the characters "

This method also works for negative numbers and decimals!

$ text = "-1234.56"

Examine (addr ($ text))

Exchange Color (F, X, Y, B, Q, Z)

Swaps a color of an image (all pixels with that color) by a different color.

Q: Long - Handle of the target bitmap (HDC) or 0

X: Long - X offset to the screen

Y: Long - Y offset to the screen

B: Long - one with a handle

Q: Long - Source Color

Z: Long - Target Color

Result: Long - 0

B, all pixels in the byte array with the source color Q be recolored with color Z.

X and Y specify the upper-left corner of the graph B is copied to the recolour for F. The

Size of the new rectangle to be colored stems from the size of the bitmap in InitFX () / CreateFX ()

was specified.

For F one of profane can either be specified or a bitmap, with LoadFileImage () /

CreateImage ()

not brought to the screen.

Color Exchange () is pretty fast and works in real time.

Before the function can be used, must be a preparation with

The data in the byte array B are changed by calling this function ..

Example:

(a test image is loaded (with the yellow colors, red, blue, gray and white) and in the left pane

copied. Then four colors of the image are (yellow, red, blue and gray), colored purple and the other side

Pane copied.)

$ text = "test.bmp"

LoadFileImage hdc = & (addr ($ text))

Paint Image (% hdc, 0,0,444,356, hdc &, 0,0,0)

= array & InitFX (hDC &)

Exchange Color (0,0,0, & array, RGB (255,255,0), RGB (255,0,255)) 'yellow to

Color Exchange (0,0,0, & array, Rgb (255,0,0), RGB (255,0,255)) 'red to violet

Exchange Color (0,0,0, & array, Rgb (0,0,255), RGB (255,0,255)) 'blue to purple

Color Exchange (% hdc, 448.0, array &, RGB (153,153,153), RGB (255,0,255)) 'gray to

Violet and image copy to% hdc, X = 448, Y = 0

FreeFX (array &)

FreeImage (hdc &)

ExchangeRgb (F, X, Y, A, R, G, B)

It strengthens or weakens from the color channels red, green and / or blue. A kind Lighten (), or

Darken (), and also used for individual color channels.

Q: Long - Handle of the target bitmap (HDC) or 0

X: Long - X offset to the screen

Y: Long - Y offset to the screen

A: Long - one with a handle

Ar rays (source bitmap)

R: Long - Gain (plus) or mitigation (minus) for the red channel

(Values from -255 to 255)

G: Long - gain (plus) or mitigation (minus) for the green color channel

(Values from -255 to 255)

B: Long - Gain (plus) or mitigation (minus) for the blue color channel

(Values from -255 to 255)

Result: Long - 0

The individual color components red, green and blue can do more with this feature or

be weakened.

X and Y specify the upper left corner, from which the effect will be brought to the screen. The size of the

Effect arises from the size of the bitmap that was specified in InitFX () / CreateFX ().

For F one of profane can either be specified or a bitmap, with LoadFileImage () /

CreateImage () was created. If passed, but for R 0, the function will be executed but

not brought to the screen.

R, G and B take values from -255 to 255. While minus values cause that this channel

abgeschächt is, and plus values, that the Kanl is strengthened. A zero means that this channel is not

changed. The farther the values of R, G and B is zero, the more visible the effect.

Before ExchangeRgb () can be applied must be a preparation with InitFX () have taken place.

The data in the byte array A will be changed by calling this function.

ExchangeRgb () replaced at bottom

can be easily simulated.

ExchangeRGB (0,0,0, array & strengthen, 1,0,0) 'red light

ExchangeRGB (0,0,0, & array, 0,0, -20) 'Blue considerably weaken

ExchangeRGB (0,0,0, dyeing & array, 255,255,255) 'Completely white

ExistSprite (H)

Tests whether the sprite with the handle H still exists.

H: Long - one with a handle InitSprite () generated sprites

Result: Long - 0 = yes, still exists / -1 = no, the sprite has been deleted (Delete)

Because even some of the functions are automated, it can be to the times they want to know whether a sprite

still exists. They can learn herewith.

But even if they work by accident with a sprite handler, there is no longer (forExample, when

Use of CollideMore), the matter will then only have no effect. The internal structure remains Sprite

persist until the last sprite has been deleted or

all structures shall be removed from memory.

ExistSprite (& sprite)

ExportPng (P, D, B, H)

Exported PNG files with 8/16-Bit-Alphakanal.

P: Long - pointer to a png handle created using

D: string (or area), which contains the filename of the PNG file

B: long - width of the PNG image P

H: Long - the amount of the PNG image P

Results: Long - Number of bytes written to file D.

These

on a folder and file name to write the png image.

Since the Png handle only contains the actual data of the PNG image, additional information on the

Export needed: B and H are the dimensions of the image.

Example:

$ text = "name.png"

ImportPng & pnghandle = (addr ($ text), addr (& width), addr (& height), addr (number & bytes))

$ text = "neuername.png"

(count = bytes & & ExportPng pnghandle, addr ($ text), & width, & height)

External Bitmaps

• CreateImage
• LoadFileImage
• LoadMemoryImage
• LoadResourceImage
• ColorFillImage
• Curve
• Frame
• FreeAllImages
• FreeImage
• GetHeightImage
• GetInfosImage
• GetWidthImage
• Paint Image
• RotateImage
• SaveImage
• SizeImage

FindBytes (B, O, A, S, L)

A copy of the Secular function MemPos, but has two Paramerter longer runs but starting from 5 and Secular

is about 100 times faster!

B: Long - range variable

O: Long - offset to the field

A: long - number of bytes in the crawler

P: Long - pointer to a search string (from Secular 7) or second range variable, suchB. Addr (string)

L: long - length of the string or the second area, suchB. Len (string)

Result: Long - Directory, or -1 if the string is not found.

With this function, any string can be searched in an area.

Example:

# string area, 700,000 describe = "Frank," 'the area with the bytes "Frank" here with 800,000 dimensioned

$ text = "Frank" 'Set the search string "Frank" Create

x & = (# FindBytes sector, 0.800000, Addr ($ text), Len (text $)) 'x & now shows 700,000 to

FindBytesCount (B, O, A, S, L, C)

An extension of the function

B: Long - range variable

O: Long - offset to the area

A: Long - Number of bytes in the crawler

S: Long - pointer to a search string (from Secular 7) or second range variable, suchB. Addr (string)

L: Long - length of the string or the second area, suchB. Len (string)

C: Long - the number of occurrences of S. Nullbasierend

Result: Long - Directory, or -1 if the string is not found.

With this function, any string can be searched in an area. This may

be specified, is meant by the reference number will.

For example, to find a specific line in a text file:

$ text = "Filename" 'Filename

(bytes = FileSize & text $) 'length of the file to determine (as an example, 48,030

Bytes)

Dim range #, & bytes' area dimensioned for file

ReadFileFast (addr ($ text), area #, 0, bytes Load &) 'File

text $ = Chr $ (13) 'search string (CR).

x & = FindBytesCount (area #, 0, & bytes, Addr (text search $), 1.146) 'Line 146

& +2 & x = x 'CR and LF skip

FindJoystick (N)

Checks to see if a joystick (1 or 2) is present.

N: Long - the number of joysticks, 1 or 2

Result: Long - joystick 0 = absent / -1 = joystick does not exist or errors.

If it returns 0, this joystick is available. Upon return of -1 can not joystick this

be used. He is either not present or not (properly installed).

x & = FindJoystick (1)

FINDPATH (B, BA, W, X1, Y1, X2, Y2, F)

This function finds a way into a pixel graphic (bitmap). Thanks to artificial intelligence is a relatively

found a short way, where black areas in the bitmap barriers and white areas walkable

Bodies labeled.

B: Long - pointer to a memory area (range variable), which has become operational later Wegdaten

BA: Long - pointer to a byte array (bitmap), which was created with InitFX ()

W: long - Wegbreite, we will search for a path of least W pixels wide / high (1 - ...)

X1: Long - X position within the bitmap, from which the search starts (starting point)

Y1: Long - Y position in the bitmap, from which the search starts (starting point)

X2: Long - X position within the bitmap, from where the search ends (target point)

Y2: Long - Y position within the bitmap, from where the search ends (target point)

Q: Long - Flags

Results: Long

-1 = An error has occurred (memory shortage)

0 = No path found

> 0 = number of bytes of Wegdaten generated in B. A value of