[BitPim-devel] a quick(?) question

[Jerad Clark]

I was checking out the current PM-325 code, which reads the phone book
data with no apparent issues, and I find that when I double-click an
entry and get the "Edit PhoneBook Entry" window, that under the
numbers tab -> number details -> type, they all default to none, even
though all my numbers have a type displayed in the main window.

Is this a bug in the 325 code, a bug in BitPim's number cleaner ( I
noticed all the dashes in the numbers are gone),

[Stephen Wood]

Not sure if this is the problem, but in p_lgpm325.p, there is a line:

numbertypetab=( 'Mobile', 'Home', 'Office', 'fax', 'pager' )

I believe that the number types should not be capitalized. Try changing the
line to:

numbertypetab=( 'mobile', 'home', 'office', 'fax', 'pager' )

and then before running bitpim, do

python2.3 protogen.py p_lgpm325.p

(This "compiles" the .p file into p_lgpm325.py)

If that helps, let me know and I will update the code. Also, if you think
the phonebook is being read properly, let me know and I will include PM325
phonebook reading in the next BitPim release. (Presently it will only run
from from source, but not compiled releases.)

I think where you see dashes in numbers, they are put there by a pretifier.
Internally, and in the phonebook editor, it is just numbers (and perhaps *,
# and pauses).

Stephen

PS, if the author of the PM325 code has any updates, please post them.

Post by Jerad Clark
I was checking out the current PM-325 code, which reads the phone book
data with no apparent issues, and I find that when I double-click an
entry and get the "Edit PhoneBook Entry" window, that under the
numbers tab -> number details -> type, they all default to none, even
though all my numbers have a type displayed in the main window.
Is this a bug in the 325 code, a bug in BitPim's number cleaner ( I
noticed all the dashes in the numbers are gone), or is this by design?
Thanks,
Jerad Clark

[Jerad Clark]

Home and Office show up correctly now, mobiles number still show as none.

Jerad Clark

Post by Stephen Wood
numbertypetab=( 'Mobile', 'Home', 'Office', 'fax', 'pager' )
I believe that the number types should not be capitalized. Try changing
numbertypetab=( 'mobile', 'home', 'office', 'fax', 'pager' )
and then before running bitpim, do
python2.3 protogen.py p_lgpm325.p
(This "compiles" the .p file into p_lgpm325.py)
If that helps, let me know and I will update the code. Also, if you think
the phonebook is being read properly, let me know and I will include PM325
phonebook reading in the next BitPim release. (Presently it will only run
from from source, but not compiled releases.)
I think where you see dashes in numbers, they are put there by a pretifier.
Internally, and in the phonebook editor, it is just numbers (and perhaps *,
# and pauses).
Stephen
PS, if the author of the PM325 code has any updates, please post them.

Post by Jerad Clark
I was checking out the current PM-325 code, which reads the phone book
data with no apparent issues, and I find that when I double-click an
entry and get the "Edit PhoneBook Entry" window, that under the
numbers tab -> number details -> type, they all default to none, even
though all my numbers have a type displayed in the main window.
Is this a bug in the 325 code, a bug in BitPim's number cleaner ( I
noticed all the dashes in the numbers are gone), or is this by design?
Thanks,
Jerad Clark

--
All the evil in this world is a

[Jerad Clark]

It seems BitPim doesn't have a mobile option in the dropdown, so if
mobile is changed to "cell", it works.

I don't know what, if any confusion that would cause with the phone
saying "mobile" and BitPim changing it to "cell" though.

Jerad

Post by Jerad Clark
Home and Office show up correctly now, mobiles number still show as none.
Jerad Clark

Post by Stephen Wood
numbertypetab=( 'Mobile', 'Home', 'Office', 'fax', 'pager' )
I believe that the number types should not be capitalized. Try changing
numbertypetab=( 'mobile', 'home', 'office', 'fax', 'pager' )
and then before running bitpim, do
python2.3 protogen.py p_lgpm325.p
(This "compiles" the .p file into p_lgpm325.py)
If that helps, let me know and I will update the code. Also, if you think
the phonebook is being read properly, let me know and I will include PM325
phonebook reading in the next BitPim release. (Presently it will only run
from from source, but not compiled releases.)
I think where you see dashes in numbers, they are put there by a pretifier.
Internally, and in the phonebook editor, it is just numbers (and perhaps *,
# and pauses).
Stephen
PS, if the author of the PM325 code has any updates, please post them.

Post by Jerad Clark
I was checking out the current PM-325 code, which reads the phone book
data with no apparent issues, and I find that when I double-click an
entry and get the "Edit PhoneBook Entry" window, that under the
numbers tab -> number details -> type, they all default to none, even
though all my numbers have a type displayed in the main window.
Is this a bug in the 325 code, a bug in BitPim's number cleaner ( I
noticed all the dashes in the numbers are gone), or is this by design?
Thanks,
Jerad Clark

--
All the evil in this world is a denial of what is true.

--
All the evil in this wor

[Stephen Wood]

Post by Jerad Clark
It seems BitPim doesn't have a mobile option in the dropdown, so if
mobile is changed to "cell", it works.
I don't know what, if any confusion that would cause with the phone
saying "mobile" and BitPim changing it to "cell" though.
Your right, the valid BitPim types are 'home', 'office', 'cell', 'fax',

'pager', 'data', and 'none'. If the phone has a "Work" type, it is mapped to
"office". "Mobile" is mapped to "cell".

Shouldn't cause the phone any confusion.

I updated the CVS with the proper types.

Stephen

[Jerad Clark]

well, I meant more along the lines of confusion for the user, rather
then confusion for the phone.

The changes to cvs look good. As a final test for reading in the
phonebook, I'll change some data on the phone and try a merge into the
local data.

But that will have to wait until later this evening. If there are any
other reading phonebook kinda tests you would like me to try as well,
just let me know.

Thanks for the help so far!
Jerad Clark

Post by Jerad Clark

Post by Jerad Clark
It seems BitPim doesn't have a mobile option in the dropdown, so if
mobile is changed to "cell", it works.
I don't know what, if any confusion that would cause with the phone
saying "mobile" and BitPim changing it to "cell" though.

Your right, the valid BitPim types are 'home', 'office', 'cell', 'fax',
'pager', 'data', and 'none'. If the phone has a "Work" type, it is mapped
to "office". "Mobile" is mapped to "cell".
Shouldn't cause the phone any confusion.
I updated the CVS with the proper types.
Stephen

--
All the evi

[Brent Roettger]

<html><div style='background-color:'><DIV class=RTE> <P>Stephen &amp; Jerad</P> <P>Thanks for taking a look at the code and testing it out.&nbsp; Unfortunately I haven't had a chance to work on it much the last couple of weeks.&nbsp; On the plus side, my machine has stopped crashing every 5 minutes since I put in a new power supply last night.&nbsp; I will have some updates in the next week or so.</P> <P>Brent Roettger<BR><BR></P></DIV> <DIV></DIV> <BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #a0c6e5 2px solid; MARGIN-RIGHT: 0px"><FONT style="FONT-SIZE: 11px; FONT-FAMILY: tahoma,sans-serif"> <HR color=#a0c6e5 SIZE=1> <DIV></DIV>From:&nbsp;&nbsp;<I>Stephen Wood &lt;***@gmail.com&gt;</I><BR>Reply-To:&nbsp;&nbsp;<I>bitpim-***@lists.sourceforge.net</I><BR>
<DIV></DIV><BR>
<DIV></DIV>PS, if the author of the PM325 code has any updates, please post them.<BR>
<DIV></DIV><BR>
<DIV></DIV><BR>
<DIV></DIV></BLOCKQUOTE></FONT>
<BLOCKQUOTE></BLOCKQUOTE></div></html>