Active Topics
-
Maemo repository (5)
to Community by dredlok706 - 1 day, 18 hrs ago -
Re-commissioning N9 in 2018 (127)
to MeeGo / Harmattan by smatkovi - 1 day, 21 hrs ago -
Porting apps to Leste (41)
to Maemo 7 / Leste by Arno_11 - 2 days, 14 hrs ago -
List of well performing apps on Leste (33)
to Maemo 7 / Leste by teroyk - 2 days, 23 hrs ago -
N900 is not recognizable on any of my devices (windows 10,7, xp) What can I do? (1)
to Nokia N900 by nieldk - 4 days, 3 hrs ago - more...
 |
|
2010-02-20
, 04:24
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#1132
|
When your bugfix doesn't seem like its enough, maybe you forgot to apply it? I fixed Maemo 5 on my device but forgot to copy it to where I upload to extras. I just pushed 1.1.4 out to the auto-builder
Yeah, I've been playing with it trying to determine how to make it bigger and feel happy with myself.
2. Maemo 4.1 users shouldn't be voting on Maemo 5 applications because there are differences that can break applications.
- Bugfix from 1.1.0: Scroll to bottom when removing a recipient
- Bugfix for 1.1.3: Maemo 5 fix was incomplete
Originally Posted by Addison
Hmm, I might have a bug with the displaying of an error.
I'm not getting a single error there chief.
Originally Posted by Addison
I recommend filing enhancements about the problem and then we can work on how to solve it. My preference, if I work on it, is to figure out when the OSK is displayed and auto-scroll the box for the user. I like the layout of the box being on the bottom.
Can I file a feature request to have the SMS text entry window to appear at the top of the screen? I still need to consistently mess around with the scrolling so that the text being typed isn't below the hildon keyboard. It's a fluffy request so if you're disenfranchised about the idea, I'll completely understand.
Originally Posted by Addison
I do agree. I've had mixed feelings about implementing it that way. It was the quickest way to do it at the time. File an enhancement about that.
It's a little weird to dial a number, click okay and then choose to dial it.
Also, with that icon being so small, it looks like it's taking a step back from ever becoming 100% finger friendly.
Yeah, I've been playing with it trying to determine how to make it bigger and feel happy with myself.
Originally Posted by Addison
1. I've not put this in extras-testing yet
Do you want us to vote on this to push it into Extras?
2. Maemo 4.1 users shouldn't be voting on Maemo 5 applications because there are differences that can break applications.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
| The Following 3 Users Say Thank You to epage For This Useful Post: | ||
 |
|
2010-02-20
, 05:59
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#1133
|
Okay. For call history, the reason why I'm not able to dial out correctly, is none of my previous numbers I have called in the past have a 1 in front of them.
So instead of DC dialing
1 517 555 5555
it's only dialing
517 555 5555
Could that be the issue, Ed?
EDIT:
Okay. I'm 0 for like 20 with calling out either by History or by dialing directly with the Keypad.
No error message on screen.
No error message either when running it through Xterm.
SMS texting is working great!
Poops.
Last edited by Addison; 2010-02-20 at 07:25.
So instead of DC dialing
1 517 555 5555
it's only dialing
517 555 5555
Could that be the issue, Ed?
EDIT:
Okay. I'm 0 for like 20 with calling out either by History or by dialing directly with the Keypad.
No error message on screen.
No error message either when running it through Xterm.
SMS texting is working great!
Poops.
Last edited by Addison; 2010-02-20 at 07:25.
|
|
2010-02-20
, 06:05
|
|
Posts: 328 |
Thanked: 101 times |
Joined on Dec 2009
|
#1134
|
1.1.14:
Yeahhh finally the sms is working again thank you Epage.
Yeahhh finally the sms is working again
thank you Epage.
|
|
2010-02-20
, 13:22
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#1135
|
Originally Posted by Addison
Due to a mistake of mine, the errors aren't being reported to the screen or log but should be seen on the command line when you run "python2.5 /usr/lib/dialcentral/dc_glade.py".
Okay. For call history, the reason why I'm not able to dial out correctly, is none of my previous numbers I have called in the past have a 1 in front of them.
So instead of DC dialing
1 517 555 5555
it's only dialing
517 555 5555
Could that be the issue, Ed?
EDIT:
Okay. I'm 0 for like 20 with calling out either by History or by dialing directly with the Keypad.
No error message on screen.
No error message either when running it through Xterm.
SMS texting is working great!
Poops.
I am going to be out for a few days so my succession of fast updates is on a hiatus.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
| The Following 2 Users Say Thank You to epage For This Useful Post: | ||
|
|
2010-02-21
, 04:42
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#1136
|
Have a great time on your few days off, you definitely deserve a break from it all.
I got it to dial out just once after about 30 attempts.
Is anyone else having weird issues calling under DC?
The only message I'm seeing is
INFO:dc_glade:Calling 1517555555
and it just hangs on that.
Same message when I did have my one, successful attempt.
I got it to dial out just once after about 30 attempts.
Is anyone else having weird issues calling under DC?
The only message I'm seeing is
INFO:dc_glade:Calling 1517555555
and it just hangs on that.
Same message when I did have my one, successful attempt.
|
|
2010-02-21
, 16:09
|
|
Posts: 1,048 |
Thanked: 979 times |
Joined on Mar 2008
@ SF Bay Area
|
#1137
|
Originally Posted by Addison
I've successfully dialed out almost always. The few times I haven't is because of PEBKAC and lack of phone connectivity.
I got it to dial out just once after about 30 attempts.
Is anyone else having weird issues calling under DC?
|
|
2010-02-23
, 00:09
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#1138
|
Originally Posted by Addison
Hangs as in the app can't do anything or just doesn't do anything?
Have a great time on your few days off, you definitely deserve a break from it all.
I got it to dial out just once after about 30 attempts.
Is anyone else having weird issues calling under DC?
The only message I'm seeing is
INFO:dc_glade:Calling 1517555555
and it just hangs on that.
Same message when I did have my one, successful attempt.
I've uploaded 1.1.5 which fixes some error reporting
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
| The Following 2 Users Say Thank You to epage For This Useful Post: | ||
|
|
2010-02-23
, 03:45
|
|
Posts: 3,811 |
Thanked: 1,151 times |
Joined on Oct 2007
@ East Lansing, MI
|
#1139
|
Originally Posted by epage
Hi Ed.
Hangs as in the app can't do anything or just doesn't do anything?
I've uploaded 1.1.5 which fixes some error reporting
My first attempt with your latest version was a success, a dozen times after that, no such luck.
Still not getting an error in either DC or in Xterm.
The only message in Xterm is that it's dialing, same as I previously mentioned.
Can you test something for me?
Call out in DC. When Google Voice rings your tablet, don't answer it, just hang up.
Try to call out again after that and see if you run into the same issue as mine.
Thanks.
|
|
2010-02-23
, 13:34
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#1140
|
Originally Posted by Addison
Could you send me a copy of the log so I can check for anything that might seem out of place to me?
Hi Ed.
My first attempt with your latest version was a success, a dozen times after that, no such luck.
Still not getting an error in either DC or in Xterm.
The only message in Xterm is that it's dialing, same as I previously mentioned.
Can you test something for me?
Call out in DC. When Google Voice rings your tablet, don't answer it, just hang up.
Try to call out again after that and see if you run into the same issue as mine.
Thanks.
__________________
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
770, n810, n900, Ideapad S10-3t
TheOneRing, DialCentral, Gonvert, Quicknote, Multilist, ejpi, nQa, Waters of Shiloah
Programming Blog
I probably have too much junk running all at the same time if you're not having any issues with it.
I'll lighten up on the CPU load and see if that's what was causing nothing to happen after dialing.
Can I file a feature request to have the SMS text entry window to appear at the top of the screen? I still need to consistently mess around with the scrolling so that the text being typed isn't below the hildon keyboard. It's a fluffy request so if you're disenfranchised about the idea, I'll completely understand.
I can test this out more tomorrow but it really looks good so far.
It's a little weird to dial a number, click okay and then choose to dial it.
Also, with that icon being so small, it looks like it's taking a step back from ever becoming 100% finger friendly.
No one has responded on hacking the hildon keyboard yet so getting that fully functional, finger friendly input for DC might not happen anyway.
Do you want us to vote on this to push it into Extras?