![]() |
Re: work in progress: simple vertical sms app: vertsms
If you don't mind, where do you use seq_id? That seems to be the last variable set from the sqlite related code.
FWIW, I removed the sqlite from gvSMS and it didn't seem to change the behavior. While I'm at it, ADDR_TYPE of 129 seems to be required for T-Mobile domestic (US) numbers. Using 132 fails. I tried to use your international support. Then to make things more interesting, ADDR_TYPE 129 or 132 works fine on AT&T domestic numbers. Quote:
Frank |
Re: work in progress: simple vertical sms app: vertsms
seq_id is given to api command. there is no direct requirement but if it works without it, the rtcom-eventlogger probably creates one automatically. but it needs to be unique number in database or problems will probably come.
just realized what is wrong in new sms.py: it outputs 8bit text but of course sms is 7 bit :D e: is there a easy way to convert? |
Re: work in progress: simple vertical sms app: vertsms
Should the existing code:
put_to_sent_sms(own_number, number, 0, strippednumber, message) be: put_to_sent_sms(own_number, number, seq_id, strippednumber, message) ? Quote:
|
Re: work in progress: simple vertical sms app: vertsms
what's that? help!
~ $ python /opt/vertsms/vertsms_gui.py response was: -5 Traceback (most recent call last): File "/opt/vertsms/vertsms_gui.py", line 422, in send s = sms.SMS(text, number) File "/opt/vertsms/vertsms/sms.py", line 125, in __init__ self.write_to_rtcomm(msg, number) File "/opt/vertsms/vertsms/sms.py", line 226, in write_to_rtcomm cursor.execute('SELECT id FROM Events') sqlite3.OperationalError: no such table: Events |
Re: work in progress: simple vertical sms app: vertsms
Quote:
|
Re: work in progress: simple vertical sms app: vertsms
1 Attachment(s)
hello
I translated the program to Arabic language Please help me I have a problem When selecting the second character of any number deletes the entered text Please i need to solution of the problem http://store1.up-00.com/May10/YsW59598.png |
Re: work in progress: simple vertical sms app: vertsms
Quote:
|
Re: work in progress: simple vertical sms app: vertsms
If the sqlite code stays, you'll also need to take into account the name change between PR1.2 and PR1.x. Maybe the below?
Quote:
|
Re: work in progress: simple vertical sms app: vertsms
Quote:
now, it save the message in conversation, but it's not received by the recipient! vertsms gui says me: it was not possible to send the message to.. (or samething like that..) |
Re: work in progress: simple vertical sms app: vertsms
i am so pissed to this forum at this moment so I will be at radio silence. and further developing vertsms will be done but more slowly.
I will add settings to the gui so one can configure TON themselves. that should stop errors with message sending but it requires user interaction at first. this comes after I get that frigging PDU string creation working... and about my decision.. you can thank the mother****ers here personally who only b*tch until they get tired and switch to whining. and when they get tired to whining, they restart the b*tching. I am trying to be happy but their negativity spreads like a disease here. Might not come back until meego is up and running, but we'll see. |
All times are GMT. The time now is 13:37. |
vBulletin® Version 3.8.8