Hi

How are we going with this?

For me, the problem of long save times is now exacerbated due to having the additional F6 to transfer:

F5 runs the emulator for client projects

F6 sends to transfer, added for server projects

After doing a lot of server scripting, when now working on a client script I am constantly pressing F6 when I am on client projects, have to wait till it does its thing, which can be 30 seconds for a large project, and then hit F5 which is what I really wanted. This is wasting so much time!

What is even more frustrating is after doing a save to send to transfer, when I then correctly hit emulator it does a save again - when nothing has changed.

Is this scheduled to be looked at soon?

Thanks

Can you please add this to the JS Handbook, and the code completion in the JS editor

Thanks :)

Re

"Considereing async nature of js event-driven env.The major issue that I am concerned with is that I have two http devices I want to sync their responses and wait for each of them to resolve"

So you might have something like:

- 2 x global variable outside both drivers with possible values 0 - sending, 1 - positive response, 2 - negative response

- 2 x EVENT_RECEIVE_TEXT, setting the global variable to 1 or 2

- send command to set global variable to 0

- have an IR.SetInterval started on send and checking regularly to see if value of each of the variable have changed.

- You might also set a time out that says after eg 20 or so seconds of sending it is a negative response.

I am not a JavaScript expert so there may be a better way to do this :)

You would monitor the feedback in EVENT_RECEIVE_TEXT as you identified, and it depends on the format of your responses as to how you would break it up and examine whether it was successful or not

You may want to not send the next request until the response is received, or build this in as a debug option :)

Have a look at the weather javascript module for an example using JSON

Sorry not sure what you mean. What do you want to do?

Hi

http://dev.iridiummobile.net/Systems_API/en#IR.RemoveListener

cheers

Hi

I would try false first; as looks to be a string of data:

commands[1]="0; Myhome; *1*1*11##,13; false.";

cheers

Hi

The port for the server is usually 30464, unless you have changed the port in the server?

Hi, probably as this is created in a newer version of iRidium ( 1.0.6.19081) so if you update your iRidium it should be ok :)

I have more work on this, and the PC itself will not turn off the screen when the power option to turn off the display is set.

So I am assuming both PC not turning off display and iRidium not doing time out screen are triggered by the same system message and thus the problem is related.

I have an identical PC here that I will put Windows on to test and see if it is the particular PC onsite or type of PC.

I will get back to you with what I find :)