AddinData function
The AddinData function is used by TV's server to get all the inforation of a Add-in.
The AddinData function should be exported in every add-in for TV's server.
Syntax
AddinData(
DWORD Request
DWORD Reserved/TCPv);
Parameters
Request
0x4
The return value must be the add-in protocol version (currently 0x00000001).
0x8
The return value must be the add-in type (0x4, 0x8 or 0xC).
0xC
Type 1(0x4)
The return value must be a pointer to a dubbel NULL byte terminated string that contains the protecols when the server should call the add-in.
Example: PUT*ZeroByte*GET*ZeroByte**ZeroByte*.
The server will call the add-in if the request start with PUT or GET.
The string can also contain * (with 2 zero bytes afther it), this will let the server call the addin handler on every request.
Type 2(0x8)
The return value must be the time (in miliseconds) that the server should wait until call the handle function again
Type 3(0xC) (Avaidable since version 1.06.2)
It should return the same as type 1, a pointer to a string with the protocols ending with 2 zero bytes. But it does use an other handler
0x11
The return value must be a pointer to the SendHandler function when is type 3, else it can be zero
This future is available since version 1.06.2
0x12
The return value must be a pointer to the EndHandler function when is type 3, else it can be zero
This future is available since version 1.08.1
0x14
The return value must be a pointer string that contains the Add-in name.
It is able to use html code.
The return value may be 0.
0x18
The return value must be a pointer string that contains the Add-in description.
It is able to use html code.
The return value may be 0.
0x1C
The return value must be a pointer string that contains the Add-in version.
It is able to use html code.
The return value may be 0.
0x20
The return value must be a pointer string that contains the Add-in creator.
It is able to use html code.
The return value may be 0.
0x24
The return value must be a pointer string that contains the Add-in status message.
It is able to use html code.
The return value may be 0.
0x28
The return value must be the status priority, if is 3 or higher it will been shown on the index-page on the administration pages.
It is able to use html code.
The return value may be 0.
0x2C
The return value must be 1 if the add-in has a configuration possibility, else return 0.
This future is available since version 1.06.1
The return value may be 0.
0x30
The return value must be a pointer to a NULL terminated string that contains html code.
The html code will be placed in a form with a button save, if the user pressed the button save the ConfigProc function will be called servial times and send the new values
This future is available since version 1.06.1
AddinData must return 1 when requesting 0x2C to enable this future
The return value may be 0.
0x34
The return value must be a pointer to a ConfigProc function
This future is available since version 1.06.1
AddinData must return 1 when requesting 0x2C to enable this future
The return value may be 0.
Reserved/TCPv
When Request is 0x4 this will 2 or 23. When this value is 2 it means the server is using TCPv4, when the value is it 23 means the server is using TCPv6. Any other value or the server version is 1.08 or older this will be Zero and will not be used.