adrnsoh / websmsdroid

Automatically exported from code.google.com/p/websmsdroid
0 stars 0 forks source link

scheduled sms in WebSMS: After having sent a scheduled message the gui indicates that it uses the same schedule settings for the next drafted message #805

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
1. Write a message and schedule it using the "send later" feature. 

2. after the message has been transferred to the sms service provider you will 
notice that the "send later" is still switched on and in the background of the 
text field the previous scheduling settings still show up. 

3. write a message and send it without touching the scheduling settings again. 

4. one would now expect that the second message has been scheduled as well. 
Instead it was sent immediately. I use the sloono connector. 

Thank you. 

Original issue reported on code.google.com by helge.kr...@gmail.com on 23 Aug 2013 at 9:59

GoogleCodeExporter commented 8 years ago
this build should fix the discrepancy between internal logic and ui.
please verify

Original comment by f...@ub0r.de on 26 Aug 2013 at 11:43

Attachments:

GoogleCodeExporter commented 8 years ago
thanks a lot! 

You seem to have fixed the display of the scheduling settings in the background 
(the background of the text field is now empty after I have sent a scheduled 
message)  but the "send later"  button at the bottom is still indicating (with 
blue color) that the previous scheduling settings are still in use for the next 
message. 

Original comment by helge.kr...@gmail.com on 27 Aug 2013 at 3:10

GoogleCodeExporter commented 8 years ago
i missed that.
this should finally fix it.

http://ub0r.de/files/bc9587cb1e05b63b48637885dcae0aaa64d95f16-WebSMS-release.apk

Original comment by f...@ub0r.de on 28 Aug 2013 at 3:07

GoogleCodeExporter commented 8 years ago
Yes, this fixed it. :-)

Thanks a lot for your support!

Original comment by helge.kr...@gmail.com on 28 Aug 2013 at 10:24

GoogleCodeExporter commented 8 years ago

Original comment by f...@ub0r.de on 16 Oct 2013 at 5:46