Problem with JSON Delete tiggzi,'s DB. Get and Create are ok by tutorial.

[Alexey Ryzhkov]

Hi. I have a problem with JSON delete function with tiggzi.
When I press buttun the delete succesfuly done only 2nd times or later. I follow tutorial http://help.gotiggr.com/getting-start...
No problem with Get or Create.
Thanks.

[maxkatz]

Do you mean the item is only deleted when you clicked a second time?

[Alexey Ryzhkov]

Hello,, Max. Thank you for relpy.
Yes. I can share project. There is no complex code.

I cant right now start programming in Eclipese cause I dont use Java before.
So it is why I try Tiggzi.

Thx!

[Alexey Ryzhkov]

I see in the Internet you have great expirience in mobile development.
I need connect mobile application with web project (possible it is a cloud).
So mobile application collect some data and send it to server side. Then server present expanded functions. I think use REST with JSON(p).
Can you recommend me how to develop mobile software?
Is it possible with Tiggzi? Is it flexible?

Thanks.
Alexey R.

[maxkatz]

Before you share, tell me exactly what happens. Do you need to click twice and only then the item is deleted?

[Alexey Ryzhkov]

Why I use tutorial. My goal is application - add to db item or any record and show me by request back. Do reports. Share data to view or edit.
What happening with tutorial:

1. Start applicaion, get messages, refresh screen. - Screen Ok, DB ok.

2. Add new item, get messages, refresh screeg. - Screen Ok, DB ok..

3. Delete any item from list, get messages, refresh screen - Screen the same, DB the same.

4. Again delete any item - Screen Ok, DB ok.

   Am I clear?

   PS:I try to understand and changed without variable now. Not work, will change back.

[Alexey Ryzhkov]

Exactly this one mention - " Do you need to click twice and only then the item is deleted? ". What reason?

[maxkatz]

After delete, how do you update the list? There are two ways to do it. First, you can invoke the get list service again (it has to be invoked on success event of delete service). Second, update the list on the client. In general, the first approach would be faster to implement, although you do send an extra request.