I use "function createString(data, timeStamp, type, isLog)" to create a cutsom console. The problem is, that the function seems to be called three times when a tcp package is displayed.
How to reproduce:
1. Start two instances of ScripCommunicator
2. Configure one as TCP Server on e.g. port 26000
3. Configure the second one as TCP client connecting to 127.0.0.1:26000
4. Create a custom console with the following code:
function createString(data, timeStamp, type, isLog)
{
var resultString = "A";
return resultString;
}
5. Send a single value from the server instance to the client instance.
6. "AAA" will appear in the console
What i would expect: The function is only called once per packet. Which would mean that only one "A" is printed.
Is use version 4.08
Regards
Simon
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "Bug Reports" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I use "function createString(data, timeStamp, type, isLog)" to create a cutsom console. The problem is, that the function seems to be called three times when a tcp package is displayed.
How to reproduce:
1. Start two instances of ScripCommunicator
2. Configure one as TCP Server on e.g. port 26000
3. Configure the second one as TCP client connecting to 127.0.0.1:26000
4. Create a custom console with the following code:
function createString(data, timeStamp, type, isLog)
{
var resultString = "A";
return resultString;
}
5. Send a single value from the server instance to the client instance.
6. "AAA" will appear in the console
What i would expect: The function is only called once per packet. Which would mean that only one "A" is printed.
Is use version 4.08
Regards
Simon
View and moderate all "Bug Reports" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Arg. I just tested with 4.09 - the issue seems to be already fixed.
Sorry!
Hi Simon,
no problem :-). And thx for reporting me the possible bug.
Best regards,
Stefan