NET SendVar - Revision history

Sandman: /* Returns */

Sandman — Tue, 02 Oct 2007 11:59:33 GMT

Returns

←Older revision		Revision as of 11:59, 2 October 2007
Line 37:		Line 37:
	\| NET_ERROR_CONNINACTIVE \|\| - The connection is inactive.		\| NET_ERROR_CONNINACTIVE \|\| - The connection is inactive.
	\|-		\|-
-	\| NET_ERROR_MESSAGETOOLONG \|\| - The ~~message~~ is too ~~long~~.	+	\| NET_ERROR_MESSAGETOOLONG \|\| - The data is too big.
	\|-		\|-
	\| NET_ERROR_SENDING \|\| - Could not send.		\| NET_ERROR_SENDING \|\| - Could not send.

Sandman: /* Definition */

Sandman — Tue, 02 Oct 2007 11:51:19 GMT

Definition

←Older revision		Revision as of 11:51, 2 October 2007
Line 13:		Line 13:

	A null character on the end is not needed:		A null character on the end is not needed:
-	NET_SendVar( netid , &~~msg~~ , sizeof(~~msg~~) );	+	NET_SendVar( netid , &data , sizeof(data_element)*elements );
		+	Or send an integer:
		+	NET_SendVar( netid , &my_int , sizeof(int) );
	Or send a struct:		Or send a struct:
	NET_SendVar( netid , mystruct , sizeof(mystruct) );		NET_SendVar( netid , mystruct , sizeof(mystruct) );

Sandman at 22:49, 12 September 2007

Sandman — Wed, 12 Sep 2007 22:49:24 GMT

←Older revision		Revision as of 22:49, 12 September 2007
Line 44:		Line 44:
	== Notes ==		== Notes ==
	Make sure the data is received properly. If you send a struct, be sure the receiver knows he should be receiving a struct and then receive the struct like it should. [[NET_RecvVar]]() is helpful for this.		Make sure the data is received properly. If you send a struct, be sure the receiver knows he should be receiving a struct and then receive the struct like it should. [[NET_RecvVar]]() is helpful for this.
		+
		+	{{Netfuncbox}}

Sandman: message -> data

Sandman — Wed, 12 Sep 2007 19:53:05 GMT

message -> data

←Older revision		Revision as of 19:53, 12 September 2007
Line 8:		Line 8:

	==Definition==		==Definition==
-	'''INT''' NET_SendVar ( <'''WORD''' connection> , <'''BYTE POINTER''' ~~message~~> , <'''INT''' length> , [<'''BYTE''' includeseparator>] )	+	'''INT''' NET_SendVar ( <'''WORD''' connection> , <'''BYTE POINTER''' data> , <'''INT''' length> , [<'''BYTE''' includeseparator>] )

-	Sends ~~a message~~ in array form or ~~send~~ a byte, word or int.	+	Sends data in array form or a byte, word or int or whatever other variable.

	A null character on the end is not needed:		A null character on the end is not needed:
Line 21:		Line 21:
	\| '''WORD''' connection \|\| - The connection identifier.		\| '''WORD''' connection \|\| - The connection identifier.
	\|-		\|-
-	\| '''BYTE''' ~~pointer message~~ \|\| - The pointer to the ~~message~~/variable.	+	\| '''BYTE POINTER''' data \|\| - The pointer to the data/variable.
	\|-		\|-
-	\| '''INT''' length \|\| - The length/size of the ~~message~~/variable.	+	\| '''INT''' length \|\| - The length/size of the data/variable.
	\|-		\|-
-	\| ['''BYTE''' includeseparator] \|\| - [[true]]/[[false]]: whether the connection's separator will be added to the ~~message~~ at the end. Default is true.	+	\| ['''BYTE''' includeseparator] \|\| - [[true]]/[[false]]: whether the connection's separator will be added to the data at the end. Default is true.
	\|}		\|}

Sandman: New page: Category:functions Category:networkdll Category:dll '''Up to Network.DLL Functions''' ---- ==Definition== '''INT''' NET_SendVar ( <'''WORD'''...

Sandman — Wed, 12 Sep 2007 19:49:44 GMT

New page: Category:functions Category:networkdll Category:dll '''Up to Network.DLL Functions''' ---- ==Definition== '''INT''' NET_SendVar ( <'''WORD'''...

New page

[[Category:functions]]
[[Category:networkdll]]
[[Category:dll]]

[[Functioncategory:Networkdll|'''Up to Network.DLL Functions''']]
----

==Definition==
'''INT''' NET_SendVar ( <'''WORD''' connection> , <'''BYTE POINTER''' message> , <'''INT''' length> , [<'''BYTE''' includeseparator>] )

Sends a message in array form or send a byte, word or int.

A null character on the end is not needed:
NET_SendVar( netid , &msg , sizeof(msg) );
Or send a struct:
NET_SendVar( netid , mystruct , sizeof(mystruct) );

== Parameters ==
{|
| '''WORD''' connection || - The connection identifier.
|-
| '''BYTE''' pointer message || - The pointer to the message/variable.
|-
| '''INT''' length || - The length/size of the message/variable.
|-
| ['''BYTE''' includeseparator] || - [[true]]/[[false]]: whether the connection's separator will be added to the message at the end. Default is true.
|}

== Returns ==
'''INT''' : The size of the succesfully sent data. With the separatorlength, if the separator was added.
{|
| NET_ERROR_INVALIDCONN || - The connection is invalid.
|-
| NET_ERROR_CONNINACTIVE || - The connection is inactive.
|-
| NET_ERROR_MESSAGETOOLONG || - The message is too long.
|-
| NET_ERROR_SENDING || - Could not send.
|-
| >=0 || - The size of the succesfully sent data. With the separatorlength, if the separator was added.
|}

== Notes ==
Make sure the data is received properly. If you send a struct, be sure the receiver knows he should be receiving a struct and then receive the struct like it should. [[NET_RecvVar]]() is helpful for this.