Bug or feature?
I’m using native.setactivityindicator true/false.
With an http GET it works as advertised but when used in conjunction with a socket call it does not.
I.e.
[lua]native.setactivityindicator( true)
reply = socketfunction(some xml data)
– have tried:
– native.setactivityindicator(false) in the socketfunction
– and also as:
native.setactivityindicator( true)
reply = socketfunction(some xml data)
native.setactivityindicator( false)[/lua]
neither works.
Am I using it wrong?
Basically all I want is to show something that a server connect is being attempted. Not a concern if the user entered the correct IP and the server is up as connection is fast enough. It’s when the IP is entered wrong or the server is down that I want to show something to the user that the app is trying to connect.
Turns out that I’m encountering more trouble user proofing the app than building the ‘working’ part, but I guess that’s to be expected. 
[import]uid: 6547 topic_id: 9527 reply_id: 309527[/import]