The Following User Says Thank You to gri For This Useful Post: | ||
![]() |
2010-08-09
, 22:51
|
|
Posts: 141 |
Thanked: 5 times |
Joined on Dec 2009
@ Brasil
|
#42
|
![]() |
2010-09-02
, 16:34
|
Posts: 75 |
Thanked: 78 times |
Joined on Jan 2010
@ Germany
|
#43
|
![]() |
2010-09-04
, 10:24
|
Posts: 75 |
Thanked: 78 times |
Joined on Jan 2010
@ Germany
|
#44
|
![]() |
2010-09-04
, 16:49
|
|
Posts: 417 |
Thanked: 200 times |
Joined on Apr 2010
@ Germany
|
#45
|
![]() |
2010-09-06
, 18:35
|
Posts: 190 |
Thanked: 129 times |
Joined on Mar 2010
@ Bavaria, Germany
|
#46
|
Which of the plugins is the most "complete" one (i.e. with balance, different message types, multiple receipients, good error checking & reporting, etc)?
I don't have accounts for any of these providers, but if I know the most complete plugin, I would create an account to be able to figure stuff out for myself…
And another enhancement request:
Would it be possible to distinguish SMS sent by this tool from normal SMS in the eventlogger-database? Maybe by using the "flag" column (is this column used by any builtin programs?)…
Would be nice, because I have a certain amount of free SMS, and I'd like to check how many I've already used…
![]() |
2010-09-06
, 20:34
|
Posts: 75 |
Thanked: 78 times |
Joined on Jan 2010
@ Germany
|
#47
|
![]() |
2010-09-07
, 16:52
|
Posts: 190 |
Thanked: 129 times |
Joined on Mar 2010
@ Bavaria, Germany
|
#48
|
The emit-stuff doesn't work in the loadSettings-Routine, that confused me…
Probably the Login-Code should be moved to another Routine, are there any login/initialization-Routines called once when starting the plugin and once when the settings are changed?
![]() |
2010-09-07
, 17:31
|
Posts: 729 |
Thanked: 155 times |
Joined on Dec 2009
|
#49
|
![]() |
2010-09-08
, 15:08
|
Posts: 75 |
Thanked: 78 times |
Joined on Jan 2010
@ Germany
|
#50
|
In case of your code: The SipgateProviderPlugin instance is created on program startup and the SipgateProvider instance is created when clicking on the account and the view changes to the message view (or the options are shown). Directly after creation of SipgateProvider, the settings are loaded. This happens before any signal is being connected to the provider. That's why your emits won't work there. SaveSettings is called when the program quits or you choose another provider from the main screen. Also login() is called when the screen changes to the message screen but there are the signals connected and logout() when changing the provider or the program quits. Login() can return if it's asynchronous or synchronous. Asynchronous shows up a progress dialog and waits until loginReply is emitted.
Edit:
I don't know if you missed it, but you should not initialize inside loadSettings() and saveSettings(). Take a look at the sip files here to see which classes and functions are available in python here. Especially take a look at the ProviderInterface base class. The example I wrote some time ago does not even use everything available.
I'm going on holidays next week for about one month, so don't expect any updates in that time