Heh, I deleted my post because I saw that you had already mentioned you'd found the fix above... But you obviously were already replying to me... Now that's developer dedication!
For voice mail playback, can you somehow scrape the link to the voice mail so it is launchable though Dialcentral? Maybe not stream the audio through DC, but allow it to launch your browser to listen to it.
I'll have to think about how I'd best like to integrate this but its a possibility. I recommend filing an enhancement request so I don't lose track of it.
Also is there any way to make the downloading of contacts in the login process optional? For the most part I use DC for SMS receive/reply. While it doesn't take long to download the contacts, for the most part it is unnecessary for some users. I rarely change my contacts as I assume many others are the same way. Can you somehow cache the contacts to a local file, and only update it with a refresh within the application. It will speed up the login process and eliminate a redundant process (for me at least).
What I did several full releases ago was it remembers what contact list you last viewed and it automatically switches to it on login. I could look into making it more delay loaded?
What I did for myself way back when was if your contacts really change that infrequently, then export your contacts to CSV and put them in "~/.dialcentral/contacts". I have thought about caching more information on startup/shutdown though. Please file an enhancement request so I don't forget.
Better yet, maybe a selectable option for the user to select their "home screen" when they launch the application. So if you are a texter like me, opening the messages tab on the boot.
I have contemplated remembering the last viewed tab and switching to it on startup. That sound like it would?
I was just about to post that it is all working now...
But it isn't.
I successfully log in, and I can see my account info and my calling history, but when I actually try to make a call, either from the dialpad or from the history tab, I get a "login failed" notice.
So close, yet...
UPDATE: Diablo gives the error, but not Fremantle. Curiouser and curiouser...
And hast thou slain the login bug?
Come to my arms, my beamish boy!
Oh frabjous day! Calloo! Callay!
I'm chortling in my joy. I just needed to delete the ~/.dialcentral directory and everything is working in both Diablo (my primary Dialcentral device) and Fremantle.
And hast thou slain the login bug?
Come to my arms, my beamish boy!
Oh frabjous day! Calloo! Callay!
I'm chortling in my joy. I just needed to delete the ~/.dialcentral directory and everything is working in both Diablo (my primary Dialcentral device) and Fremantle.
I'll go vote up v14 for Fremantle.
EDIT: oh, not in Extras-testing... Nevermind...
I'll wait one day to see for any major issues and then push it to Fremantle extras-testing and Diablo extras.
i don't have login issues with that version ,but i cannot send sms, i do receive it though.
What do you see? an error? nothing?
What tab did you open the SMS Entry dialog from?
Could you provide a copy of the log (~/.dialcentral/dialcentral.log)?
I just did some testing and didn't see any issues but most of the issues lately I haven't been able to see. Hopefully we can work together to get this resolved.
Could you provide a copy of the log (~/.dialcentral/dialcentral.log)?
I just did some testing and didn't see any issues but most of the issues lately I haven't been able to see. Hopefully we can work together to get this resolved.
Edit: Epage after restart my table Everything working fine now even sendind sms from the messages tab....Thanks keep the good work!
epage, it's working great now - no log in problems. Thanks, this is a really slick application!
(qole, I had to log in, select the call back number and time and then close and reopen the application - I think I remember this from a previous version too - then it works fine)
