Notices

For login fixes, most of the thanks go to TronDD, tgrondin, and n9ots for their patience in helping me work through this issue. The rollout of GoogleVoice that caused this break still hasn't hit me. I can login fine without the fix. Only with their cooperation was I able to determine what the potential issues were and to test the fix.

I'm glad the move worked out and I hope you. Would it would with the times if I just had Dialcentral use a random number generator with listing times messages were sent/received

In appreciation of the help I recently received I thought I'd come clean. I started working on a GoogleVoice support for Telepathy that I'm calling "The One Ring".

I have not previously announced this publicly due to lack of documentation (affects my time table) and I am concerned what the end user experience will actually be like. I don't like keeping it quiet though so I thought I'd mention this.

It is not in any kind of working state right now. I am unsure if I will build support in for RTComm for the n8x0. My main target is the Desktop and n900. Due to how slow development is going I will probably not make Maemo Summit for this. At least there should be Dialcentral available in time for Maemo Summit for the n900.

I expect the initial release will only work with people on your contact list and maybe only 1 number per contact. I hope to have both texting (including receiving voicemails as texts) and initiating calls though one or the other might be dropped for initial release.

In Summary: The One Ring is vaporware but I'm excited for it.

So epage, is this your final release for Dialcentral?

If yes, I'll go ahead and update right now.

Love, how some messages are hidden from view and when you click the message now it shows you the most recent message.

As part of my The One Ring work I will not abandon Dialcentral. It will still be important for Diablo and to fill in interface gaps in The One Ring

EDIT: To confirm this, 1.0.7-0 was released after I started The One Ring. The One Ring is meant to co-exist and not replace Dialcentral.

Hey Epage

I am also having an issue with the call back number not being accesable. Here is a screen shot. Its not an issue for me but if you have some things for me to try I'll certainly give you a hand. I noticed this on the last release as well so its not something you just recently changed, at least for me.

Knowing it was in the last release also makes me feel a bit better, that its basically been there since I first did the new callback number work.

I'll try and take a look into it tonight.

Just a hint about my old callback number problems...

Apparently, I have been "grandfathered in" to Google Voice. My Canadian callback numbers were imported from Grandcentral, but I cannot edit them nor can I add any new Canadian numbers. This is a (stupid) GV policy, not the fault of your application.

This may be why I was having problems in the first place with the callback numbers.

I have also noticed the missing callback number field.

I noticed that after I edited the settings.ini by putting in the call back number that the box for said call back number is there when the program is next started

My best guess is the Google rollout that I haven't seen yet broke my gathering of callback numbers. I'm providing something to harden against this type of situation and am going to post another script so people can grab me the list of callback numbers.