Menu
▾
▴
bitpim-devel — For bitpim developers
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
(53) |
Apr
(48) |
May
(14) |
Jun
(3) |
Jul
(21) |
Aug
(11) |
Sep
(77) |
Oct
(67) |
Nov
(28) |
Dec
(163) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(112) |
Feb
(143) |
Mar
(114) |
Apr
(138) |
May
(173) |
Jun
(119) |
Jul
(119) |
Aug
(117) |
Sep
(187) |
Oct
(170) |
Nov
(254) |
Dec
(193) |
| 2005 |
Jan
(336) |
Feb
(284) |
Mar
(189) |
Apr
(100) |
May
(89) |
Jun
(52) |
Jul
(85) |
Aug
(138) |
Sep
(181) |
Oct
(137) |
Nov
(104) |
Dec
(98) |
| 2006 |
Jan
(76) |
Feb
(106) |
Mar
(224) |
Apr
(270) |
May
(103) |
Jun
(144) |
Jul
(77) |
Aug
(38) |
Sep
(37) |
Oct
(20) |
Nov
(14) |
Dec
(73) |
| 2007 |
Jan
(130) |
Feb
(68) |
Mar
(78) |
Apr
(60) |
May
(45) |
Jun
(63) |
Jul
(84) |
Aug
(45) |
Sep
(40) |
Oct
(12) |
Nov
(71) |
Dec
(56) |
| 2008 |
Jan
(44) |
Feb
(20) |
Mar
(25) |
Apr
(17) |
May
(33) |
Jun
(60) |
Jul
(97) |
Aug
(38) |
Sep
(10) |
Oct
(20) |
Nov
(13) |
Dec
(19) |
| 2009 |
Jan
(7) |
Feb
(5) |
Mar
(23) |
Apr
(10) |
May
(6) |
Jun
(5) |
Jul
(17) |
Aug
(7) |
Sep
(14) |
Oct
(27) |
Nov
(13) |
Dec
(12) |
| 2010 |
Jan
(37) |
Feb
(9) |
Mar
(13) |
Apr
(12) |
May
(8) |
Jun
(3) |
Jul
(1) |
Aug
(9) |
Sep
(3) |
Oct
(1) |
Nov
(1) |
Dec
(4) |
| 2011 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(4) |
May
|
Jun
(2) |
Jul
(8) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
|
Jul
|
Aug
|
Sep
(5) |
Oct
|
Nov
(3) |
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(2) |
Oct
|
Nov
|
Dec
|
|
From: Mike W. <mw...@co...> - 2004-04-28 15:08:31
|
>There is a note in the version history for sanyo image downloads that >didn't make it into the help. I reads: > > <li>Started wallpaper download support for Sanyo SCP-8100 and > SCP-5500. Only camera pictures on the phone will be > downloaded. Wallpaper on the phone that was uploaded with Vision or by > cable is not yet transferred. Videos (on the SCP-5500) will be > transferred but will cause all sorts of exceptions/errors. The videos > can be found in the BitPim files directory. Please do not report > bugs. Use at your own risk. > > >On Tue, 2004-04-27 at 23:40, Mike Wells wrote: >> >> My SCP-5500 generated a "no handler for image type" >> exception pop-up right after getting the 34th image >> file. >> ... Thanks. I usually check for the caveats first. If I do notice a bug, how do I know when a report is appropriate? Is there some kind of formal demarcation for those features for which bug reports are not solicited and and those which are? Also, is there a way to qualify a report with some formalized priority so it doesn't sound nit-picky, for example? BTW, it really isn't apparent how awful these pictures are until you see them in full 640x480 res. But the convenience is great. This will soon be a social problem, I'm sure. Anyway, good work to you all on this project! I pesonally don't want to use Vision to offload my images, ringers, and video because it's quite an unnecessary expense. |
|
From: Stephen W. <sa...@us...> - 2004-04-28 12:53:57
|
I have a few minor bitfling complaints, none of which will stop me from using it and soliciting someone to flingserve the latest Sanyo phone to me. 1. The allowed addresses field on a user doesn't get remembered upon exit. I am able to edit the .bitfling file though so that it gets remembered. 2. Under linux, the little paw icon that bit fling pops up is hard to move. If I move the mouse to fast, it falls off the mouse. Since linux desktops don't really have an equivalent to the windows tray, I think I would prefer that the Bitfling GUI come up and let the user iconify it. 3. Exiting bitfling (under linux again), leaves an exception on the console. Something about un-authorized fondling? Stephen Traceback (most recent call last): File "bitfling/bitfling.py", line 313, in OnAuthListItemFondled File "/usr/lib/python2.3/site-packages/wxPython/wx.py", line 1828, in __getattr__ wxPython.wx.wxPyDeadObjectError: The C++ part of the wxButton object has been deleted, attribute access no longer allowed. Unhandled exception in thread started by <bound method BitFlingService.__bootstrap of <BitFlingService(Threading SSH server controller for :12652, stopped daemon)>> Error in sys.excepthook: TypeError: 'NoneType' object is not callable Original exception was: Traceback (most recent call last): File "/usr/lib/python2.3/threading.py", line 451, in __bootstrap File "/usr/lib/python2.3/threading.py", line 460, in __stop File "/usr/lib/python2.3/threading.py", line 256, in notifyAll File "/usr/lib/python2.3/threading.py", line 238, in notify TypeError: 'NoneType' object is not callable |
|
From: Roger B. <ro...@ro...> - 2004-04-28 06:23:48
|
Stephen Wood wrote: > Will you be able to get the comment I made about Sanyo camera downloads > in versionhistory.htd into the official build? I won't rebuild the help for the build since that then requires redoing the build. However after the build I will update the website version of the help which will then have the full details. > Traceback (most recent call last): > File "guiwidgets.py", line 448, in ApplyBitFlingSettings > File "bitflingscan.py", line 126, in decode > ValueError: invalid literal for int(): <u I will just document this and fix it for the next release. The code has a little difficulty decoding the obfuscated password when one hasn't been set already :-) Other than that it seems it all works fine so I will go ahead and release what we have. Steven, feel free to do your Mac builds. Roger |
|
From: Roger B. <ro...@ro...> - 2004-04-28 06:02:42
|
Stephen Wood wrote: > I successfully ran bitfling to different Sanyo phones. I just did a > localhost connection, but it was definitely bitfling. Cool. > I also tried to run a bitfling client from the CVS version, but the > bitfling options seem to be missing in the settings pane. I did a cvs > -d, but I probably need to go back through the postings to see if there > is something else I need to install. Yes, you have to have pycrypto installed. Details are on http://bitpim.sf.net/developer.html Roger |
|
From: bfaye <bf...@ya...> - 2004-04-28 05:54:58
|
It was discussed in a thread on howardforums.com that they are using QCELP and NOT PureVoice for the audio part, and there is no FREE decoder for QCELP. Looks dim with regards to playing the vid with audio without uploading it to Sprint first. --- Mike Wells <mw...@co...> wrote: > > > Hey this is good stuff. I think Bitpim is the first piece > of software out there that can download the 15 second "movies" > off of the SCP-5500. Had to use FFMPEG to cut out the audio > stream first before the video could be played using Quicktime, > RealNetworks, and Windows Media, however. > Are they using QCELP for the mpeg4 audio stream? > > FFMPEG reports: > Duration: 00:00:15.0, bitrate: 79 kb/s > Stream #0.0: Video: mpeg4, 128x96, 15.00 fps > Stream #0.1: Audio: 0x6134706d, 1928 Hz, stereo > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: Oracle 10g > Get certified on the hottest thing ever to hit the market... Oracle 10g. > Take an Oracle 10g class now, and we'll give you the exam FREE. > http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click > _______________________________________________ > Bitpim-devel mailing list > Bit...@li... > https://lists.sourceforge.net/lists/listinfo/bitpim-devel __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover |
|
From: Mike W. <mw...@co...> - 2004-04-28 04:53:13
|
Hey this is good stuff. I think Bitpim is the first piece of software out there that can download the 15 second "movies" off of the SCP-5500. Had to use FFMPEG to cut out the audio stream first before the video could be played using Quicktime, RealNetworks, and Windows Media, however. Are they using QCELP for the mpeg4 audio stream? FFMPEG reports: Duration: 00:00:15.0, bitrate: 79 kb/s Stream #0.0: Video: mpeg4, 128x96, 15.00 fps Stream #0.1: Audio: 0x6134706d, 1928 Hz, stereo |
|
From: Stephen W. <sa...@us...> - 2004-04-28 04:40:48
|
There is a note in the version history for sanyo image downloads that
didn't make it into the help. I reads:
<li>Started wallpaper download support for Sanyo SCP-8100 and
SCP-5500. Only camera pictures on the phone will be
downloaded. Wallpaper on the phone that was uploaded with Vision or by
cable is not yet transferred. Videos (on the SCP-5500) will be
transferred but will cause all sorts of exceptions/errors. The videos
can be found in the BitPim files directory. Please do not report
bugs. Use at your own risk.
On Tue, 2004-04-27 at 23:40, Mike Wells wrote:
>
> My SCP-5500 generated a "no handler for image type"
> exception pop-up right after getting the 34th image
> file.
>
> 23:24:41.671 COM3: Opening port COM3, 115200 baud, timeout 3.000000,
> hardwareflow 0, softwareflow 0
> 23:24:41.730 COM3: Open of comm port suceeded
> 23:24:41.740 SCP-5500: Attempting to contact phone
> 23:24:41.740 SCP-5500: Retrieving fundamental phone information
> 23:24:41.740 SCP-5500: Phone serial number
> 23:24:41.750 SCP-5500: Getting file contents 'nvm/$SYS.ESN'
> 23:24:44.775 COM3: Timed out waiting for 7e, requested bytes 1 - 0 bytes read
> 23:24:44.805 COM3: Changed port speed to 38400
> 23:24:48.309 COM3: Timed out waiting for 7e, requested bytes 1 - 0 bytes read
> 23:24:48.339 COM3: Changed port speed to 115200
> 23:24:51.855 COM3: Timed out waiting for 7e, requested bytes 1 - 0 bytes read
> 23:24:51.885 COM3: Changed port speed to 115200
> 23:24:55.401 SCP-5500: Now in brew mode
> 23:24:55.520 SCP-5500: Read 97 bytes at 7 bytes/second
> 23:24:55.520 SCP-5500: Reading wallpaper-index
> 23:24:55.540 SCP-5500: Now in phonebook mode
> 23:24:56.471 SCP-5500: Reading ringtone-index
> 23:24:56.482 SCP-5500: Fundamentals retrieved
> 23:24:57.584 SCP-5500: Getting file # 0 from directory 1
> 23:25:04.874 SCP-5500: Read 39586 bytes at 5430 bytes/second
> 23:25:04.874 SCP-5500: Getting file # 1 from directory 1
> 23:25:33.125 SCP-5500: Read 149756 bytes at 5300 bytes/second
> 23:25:33.125 SCP-5500: Getting file # 2 from directory 1
> 23:26:01.234 SCP-5500: Read 146270 bytes at 5205 bytes/second
> 23:26:01.234 SCP-5500: Getting file # 3 from directory 1
> 23:26:28.184 SCP-5500: Read 143303 bytes at 5315 bytes/second
> 23:26:28.184 SCP-5500: Getting file # 4 from directory 1
> 23:26:36.927 SCP-5500: Read 45524 bytes at 5206 bytes/second
> 23:26:36.927 SCP-5500: Getting file # 5 from directory 1
> 23:26:42.494 SCP-5500: Read 29973 bytes at 5383 bytes/second
> 23:26:42.505 SCP-5500: Getting file # 6 from directory 1
> 23:26:44.276 SCP-5500: Getting file # 7 from directory 1
> 23:26:53.029 SCP-5500: Read 44201 bytes at 5055 bytes/second
> 23:26:53.029 SCP-5500: Getting file # 8 from directory 1
> 23:26:59.378 SCP-5500: Read 33180 bytes at 5226 bytes/second
> 23:26:59.378 SCP-5500: Getting file # 9 from directory 1
> 23:27:08.903 SCP-5500: Read 49836 bytes at 5232 bytes/second
> 23:27:08.913 SCP-5500: Getting file # 10 from directory 1
> 23:27:20.819 SCP-5500: Read 55924 bytes at 5053 bytes/second
> 23:27:20.819 SCP-5500: Getting file # 11 from directory 1
> 23:27:27.920 SCP-5500: Read 41358 bytes at 5214 bytes/second
> 23:27:27.920 SCP-5500: Getting file # 12 from directory 1
> 23:27:34.499 SCP-5500: Read 33486 bytes at 5082 bytes/second
> 23:27:34.509 SCP-5500: Getting file # 13 from directory 1
> 23:27:45.996 SCP-5500: Read 60754 bytes at 5288 bytes/second
> 23:27:45.996 SCP-5500: Getting file # 14 from directory 1
> 23:27:47.989 SCP-5500: Getting file # 15 from directory 1
> 23:27:55.450 SCP-5500: Read 38827 bytes at 5203 bytes/second
> 23:27:55.460 SCP-5500: Getting file # 16 from directory 1
> 23:27:57.151 SCP-5500: Getting file # 17 from directory 1
> 23:28:06.605 SCP-5500: Read 49664 bytes at 5253 bytes/second
> 23:28:06.605 SCP-5500: Getting file # 18 from directory 1
> 23:28:34.436 SCP-5500: Read 146949 bytes at 5280 bytes/second
> 23:28:34.436 SCP-5500: Getting file # 19 from directory 1
> 23:28:45.802 SCP-5500: Read 58431 bytes at 5140 bytes/second
> 23:28:45.802 SCP-5500: Getting file # 20 from directory 1
> 23:28:55.736 SCP-5500: Read 51668 bytes at 5201 bytes/second
> 23:28:55.746 SCP-5500: Getting file # 21 from directory 1
> 23:29:04.418 SCP-5500: Read 44935 bytes at 5175 bytes/second
> 23:29:04.428 SCP-5500: Getting file # 22 from directory 1
> 23:29:15.384 SCP-5500: Read 57217 bytes at 5227 bytes/second
> 23:29:15.384 SCP-5500: Getting file # 23 from directory 1
> 23:29:41.611 SCP-5500: Read 140752 bytes at 5364 bytes/second
> 23:29:41.621 SCP-5500: Getting file # 24 from directory 1
> 23:29:53.378 SCP-5500: Read 61198 bytes at 5209 bytes/second
> 23:29:53.378 SCP-5500: Getting file # 25 from directory 1
> 23:30:03.132 SCP-5500: Read 52428 bytes at 5375 bytes/second
> 23:30:03.132 SCP-5500: Getting file # 26 from directory 1
> 23:30:10.773 SCP-5500: Read 40660 bytes at 5314 bytes/second
> 23:30:10.773 SCP-5500: Getting file # 27 from directory 1
> 23:30:17.263 SCP-5500: Read 33876 bytes at 5228 bytes/second
> 23:30:17.263 SCP-5500: Getting file # 28 from directory 1
> 23:30:27.237 SCP-5500: Read 52309 bytes at 5244 bytes/second
> 23:30:27.237 SCP-5500: Getting file # 29 from directory 1
> 23:30:35.589 SCP-5500: Read 44562 bytes at 5329 bytes/second
> 23:30:35.599 SCP-5500: Getting file # 30 from directory 1
> 23:30:43.190 SCP-5500: Read 40020 bytes at 5272 bytes/second
> 23:30:43.190 SCP-5500: Getting file # 31 from directory 1
> 23:30:54.457 SCP-5500: Read 58736 bytes at 5213 bytes/second
> 23:30:54.467 SCP-5500: Getting file # 32 from directory 1
> 23:31:02.769 SCP-5500: Read 44369 bytes at 5344 bytes/second
> 23:31:02.769 SCP-5500: Getting file # 33 from directory 1
> 23:31:11.520 SCP-5500: Read 45641 bytes at 5220 bytes/second
> 23:31:11.520 SCP-5500: Getting file # 34 from directory 1
> 23:31:13.174 ['sync', 'wallpaper-index', 'wallpapers', 'uniqueserial',
> 'ringtone-index']
> 23:31:13.174 {'wallpaper': 'OVERWRITE'}
> 23:31:18.982 Exception: An unexpected exception has occurred.
> Please see the help for details on what to do.
>
> Traceback (most recent call last):
> File "gui.pyo", line 994, in OnCallback
> File "gui.pyo", line 117, in __call__
> File "gui.pyo", line 73, in __call__
> File "gui.pyo", line 731, in OnDataGetPhoneResults
> File "wallpaper.pyo", line 201, in populate
> File "bpmedia.pyo", line 578, in SetItems
> File "bpmedia.pyo", line 556, in AddItems
> File "bpmedia.pyo", line 357, in _regenerateimagelist
> File "wallpaper.pyo", line 121, in GetItemSizedBitmap
> File "wxPython\image.pyo", line 255, in GetWidth
> wxPyAssertionError: C++ assertion "wxAssertFailure" failed in
> e:\Projects\wx2.4\src\common\image.cpp(829): invalid image
>
> Variables by last 8 frames, innermost last
>
> Frame __call__ in gui.pyo at line 73
> self = <gui.Callback instance at 0x01D73F80>
> args = (None, {'sync': {'wallpaper': 'OVERWRITE'}, 'wallpaper-index
> d = {}
> kwargs = {}
>
> Frame OnDataGetPhoneResults in gui.pyo at line 731
> self = <gui.MainWindow instance; proxy of C++ wxFrame instance at _
> updwp = True
> exception = None
> results = {'sync': {'wallpaper': 'OVERWRITE'}, 'wallpaper-index': {150
> v = 'OVERWRITE'
>
> Frame populate in wallpaper.pyo at line 201
> newitems = [{'origin': 'camera', 'name': 'V15Mar04-001.jpg', 'wp-index'
> keys = [150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161,
> k = 184
> existing = []
> dict = {'sync': {'wallpaper': 'OVERWRITE'}, 'wallpaper-index': {150
> entry = {'origin': 'camera', 'name': 'V17Apr04-002.jpg'}
> newentry = {'origin': 'camera', 'file': 'C:\\Documents and Settings\\mw
> filename = 'C:\\Documents and Settings\\mwells\\My Documents\\bitpim\\w
> self = <wallpaper.WallpaperView instance; proxy of C++ wxPanel inst
>
> Frame SetItems in bpmedia.pyo at line 578
> items = [{'origin': 'camera', 'name': 'V15Mar04-001.jpg', 'wp-index'
> self = <wallpaper.WallpaperView instance; proxy of C++ wxPanel inst
>
> Frame AddItems in bpmedia.pyo at line 556
> items = [{'origin': 'camera', 'name': 'V15Mar04-001.jpg', 'wp-index'
> self = <wallpaper.WallpaperView instance; proxy of C++ wxPanel inst
> adict = {'origin': 'camera', 'file': 'C:\\Documents and Settings\\mw
> key = 307
>
> Frame _regenerateimagelist in bpmedia.pyo at line 357
> stat = None
> img = None
> k = '__image_size'
> imgsz = None
> item = {'origin': 'camera', 'file': 'C:\\Documents and Settings\\mw
> wxil = <wxPython.gdi.wxImageList instance; proxy of C++ wxImageList
> il = [<wxPython.gdi.wxBitmapPtr instance; proxy of C++ wxBitmap i
> key = 274
> iconsz = (100, 100)
> self = <wallpaper.WallpaperView instance; proxy of C++ wxPanel inst
>
> Frame GetItemSizedBitmap in wallpaper.pyo at line 121
> width = 100
> self = <wallpaper.WallpaperView instance; proxy of C++ wxPanel inst
> item = {'origin': 'camera', 'file': 'C:\\Documents and Settings\\mw
> img = <wxPython.image.wxImage instance; proxy of C++ wxImage insta
> height = 100
>
> Frame GetWidth in wxPython\image.pyo at line 255
> _kwargs = {}
> self = <wxPython.image.wxImage instance; proxy of C++ wxImage insta
> _args = ()
>
>
> The Windows directory shows:
> 04/27/2004 11:32p 3,104 index.idx
> 04/27/2004 11:31p 146,949 MDM11Apr04-001.mp4
> 04/27/2004 11:31p 149,756 MDM16Mar04-001.mp4
> 04/27/2004 11:31p 146,270 MDM16Mar04-002.mp4
> 04/27/2004 11:31p 140,752 MDM17Apr04-001.mp4
> 04/27/2004 11:31p 143,303 MDM21Mar04-001.mp4
> 04/27/2004 11:31p 8,467 V03Apr04-001.jpg
> 04/27/2004 11:31p 49,664 V04Apr04-001.jpg
> 04/27/2004 11:31p 58,431 V11Apr04-001.jpg
> 04/27/2004 11:31p 51,668 V11Apr04-002.jpg
> 04/27/2004 11:31p 39,586 V15Mar04-001.jpg
> 04/27/2004 11:31p 44,935 V17Apr04-001.jpg
> 04/27/2004 11:31p 8,425 V17Apr04-002.jpg
> 04/27/2004 11:31p 61,198 V17Apr04-003.jpg
> 04/27/2004 11:31p 52,428 V17Apr04-004.jpg
> 04/27/2004 11:31p 40,660 V17Apr04-005.jpg
> 04/27/2004 11:31p 33,876 V18Apr04-001.jpg
> 04/27/2004 11:31p 52,309 V18Apr04-002.jpg
> 04/27/2004 11:31p 44,562 V18Apr04-003.jpg
> 04/27/2004 11:31p 40,020 V18Apr04-004.jpg
> 04/27/2004 11:31p 58,736 V18Apr04-005.jpg
> 04/27/2004 11:31p 45,524 V21Mar04-001.jpg
> 04/27/2004 11:31p 44,369 V23Apr04-001.jpg
> 04/27/2004 11:31p 45,641 V23Apr04-002.jpg
> 04/27/2004 11:31p 44,201 V26Mar04-001.jpg
> 04/27/2004 11:31p 33,180 V26Mar04-002.jpg
> 04/27/2004 11:31p 29,973 V27Mar04-001.jpg
> 04/27/2004 11:31p 49,836 V27Mar04-002.jpg
> 04/27/2004 11:31p 55,924 V27Mar04-003.jpg
> 04/27/2004 11:31p 9,130 V27Mar04-004.jpg
> 04/27/2004 11:31p 33,486 V27Mar04-005.jpg
> 04/27/2004 11:31p 60,754 V27Mar04-006.jpg
> 32 File(s) 1,827,117 bytes
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g.
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> Bitpim-devel mailing list
> Bit...@li...
> https://lists.sourceforge.net/lists/listinfo/bitpim-devel
|
|
From: Stephen W. <sa...@us...> - 2004-04-28 04:36:19
|
I successfully ran bitfling to different Sanyo phones. I just did a localhost connection, but it was definitely bitfling. I also tried to run a bitfling client from the CVS version, but the bitfling options seem to be missing in the settings pane. I did a cvs -d, but I probably need to go back through the postings to see if there is something else I need to install. |
|
From: Mike W. <mw...@co...> - 2004-04-28 03:40:57
|
My SCP-5500 generated a "no handler for image type"
exception pop-up right after getting the 34th image
file.
23:24:41.671 COM3: Opening port COM3, 115200 baud, timeout 3.000000,
hardwareflow 0, softwareflow 0
23:24:41.730 COM3: Open of comm port suceeded
23:24:41.740 SCP-5500: Attempting to contact phone
23:24:41.740 SCP-5500: Retrieving fundamental phone information
23:24:41.740 SCP-5500: Phone serial number
23:24:41.750 SCP-5500: Getting file contents 'nvm/$SYS.ESN'
23:24:44.775 COM3: Timed out waiting for 7e, requested bytes 1 - 0 bytes read
23:24:44.805 COM3: Changed port speed to 38400
23:24:48.309 COM3: Timed out waiting for 7e, requested bytes 1 - 0 bytes read
23:24:48.339 COM3: Changed port speed to 115200
23:24:51.855 COM3: Timed out waiting for 7e, requested bytes 1 - 0 bytes read
23:24:51.885 COM3: Changed port speed to 115200
23:24:55.401 SCP-5500: Now in brew mode
23:24:55.520 SCP-5500: Read 97 bytes at 7 bytes/second
23:24:55.520 SCP-5500: Reading wallpaper-index
23:24:55.540 SCP-5500: Now in phonebook mode
23:24:56.471 SCP-5500: Reading ringtone-index
23:24:56.482 SCP-5500: Fundamentals retrieved
23:24:57.584 SCP-5500: Getting file # 0 from directory 1
23:25:04.874 SCP-5500: Read 39586 bytes at 5430 bytes/second
23:25:04.874 SCP-5500: Getting file # 1 from directory 1
23:25:33.125 SCP-5500: Read 149756 bytes at 5300 bytes/second
23:25:33.125 SCP-5500: Getting file # 2 from directory 1
23:26:01.234 SCP-5500: Read 146270 bytes at 5205 bytes/second
23:26:01.234 SCP-5500: Getting file # 3 from directory 1
23:26:28.184 SCP-5500: Read 143303 bytes at 5315 bytes/second
23:26:28.184 SCP-5500: Getting file # 4 from directory 1
23:26:36.927 SCP-5500: Read 45524 bytes at 5206 bytes/second
23:26:36.927 SCP-5500: Getting file # 5 from directory 1
23:26:42.494 SCP-5500: Read 29973 bytes at 5383 bytes/second
23:26:42.505 SCP-5500: Getting file # 6 from directory 1
23:26:44.276 SCP-5500: Getting file # 7 from directory 1
23:26:53.029 SCP-5500: Read 44201 bytes at 5055 bytes/second
23:26:53.029 SCP-5500: Getting file # 8 from directory 1
23:26:59.378 SCP-5500: Read 33180 bytes at 5226 bytes/second
23:26:59.378 SCP-5500: Getting file # 9 from directory 1
23:27:08.903 SCP-5500: Read 49836 bytes at 5232 bytes/second
23:27:08.913 SCP-5500: Getting file # 10 from directory 1
23:27:20.819 SCP-5500: Read 55924 bytes at 5053 bytes/second
23:27:20.819 SCP-5500: Getting file # 11 from directory 1
23:27:27.920 SCP-5500: Read 41358 bytes at 5214 bytes/second
23:27:27.920 SCP-5500: Getting file # 12 from directory 1
23:27:34.499 SCP-5500: Read 33486 bytes at 5082 bytes/second
23:27:34.509 SCP-5500: Getting file # 13 from directory 1
23:27:45.996 SCP-5500: Read 60754 bytes at 5288 bytes/second
23:27:45.996 SCP-5500: Getting file # 14 from directory 1
23:27:47.989 SCP-5500: Getting file # 15 from directory 1
23:27:55.450 SCP-5500: Read 38827 bytes at 5203 bytes/second
23:27:55.460 SCP-5500: Getting file # 16 from directory 1
23:27:57.151 SCP-5500: Getting file # 17 from directory 1
23:28:06.605 SCP-5500: Read 49664 bytes at 5253 bytes/second
23:28:06.605 SCP-5500: Getting file # 18 from directory 1
23:28:34.436 SCP-5500: Read 146949 bytes at 5280 bytes/second
23:28:34.436 SCP-5500: Getting file # 19 from directory 1
23:28:45.802 SCP-5500: Read 58431 bytes at 5140 bytes/second
23:28:45.802 SCP-5500: Getting file # 20 from directory 1
23:28:55.736 SCP-5500: Read 51668 bytes at 5201 bytes/second
23:28:55.746 SCP-5500: Getting file # 21 from directory 1
23:29:04.418 SCP-5500: Read 44935 bytes at 5175 bytes/second
23:29:04.428 SCP-5500: Getting file # 22 from directory 1
23:29:15.384 SCP-5500: Read 57217 bytes at 5227 bytes/second
23:29:15.384 SCP-5500: Getting file # 23 from directory 1
23:29:41.611 SCP-5500: Read 140752 bytes at 5364 bytes/second
23:29:41.621 SCP-5500: Getting file # 24 from directory 1
23:29:53.378 SCP-5500: Read 61198 bytes at 5209 bytes/second
23:29:53.378 SCP-5500: Getting file # 25 from directory 1
23:30:03.132 SCP-5500: Read 52428 bytes at 5375 bytes/second
23:30:03.132 SCP-5500: Getting file # 26 from directory 1
23:30:10.773 SCP-5500: Read 40660 bytes at 5314 bytes/second
23:30:10.773 SCP-5500: Getting file # 27 from directory 1
23:30:17.263 SCP-5500: Read 33876 bytes at 5228 bytes/second
23:30:17.263 SCP-5500: Getting file # 28 from directory 1
23:30:27.237 SCP-5500: Read 52309 bytes at 5244 bytes/second
23:30:27.237 SCP-5500: Getting file # 29 from directory 1
23:30:35.589 SCP-5500: Read 44562 bytes at 5329 bytes/second
23:30:35.599 SCP-5500: Getting file # 30 from directory 1
23:30:43.190 SCP-5500: Read 40020 bytes at 5272 bytes/second
23:30:43.190 SCP-5500: Getting file # 31 from directory 1
23:30:54.457 SCP-5500: Read 58736 bytes at 5213 bytes/second
23:30:54.467 SCP-5500: Getting file # 32 from directory 1
23:31:02.769 SCP-5500: Read 44369 bytes at 5344 bytes/second
23:31:02.769 SCP-5500: Getting file # 33 from directory 1
23:31:11.520 SCP-5500: Read 45641 bytes at 5220 bytes/second
23:31:11.520 SCP-5500: Getting file # 34 from directory 1
23:31:13.174 ['sync', 'wallpaper-index', 'wallpapers', 'uniqueserial',
'ringtone-index']
23:31:13.174 {'wallpaper': 'OVERWRITE'}
23:31:18.982 Exception: An unexpected exception has occurred.
Please see the help for details on what to do.
Traceback (most recent call last):
File "gui.pyo", line 994, in OnCallback
File "gui.pyo", line 117, in __call__
File "gui.pyo", line 73, in __call__
File "gui.pyo", line 731, in OnDataGetPhoneResults
File "wallpaper.pyo", line 201, in populate
File "bpmedia.pyo", line 578, in SetItems
File "bpmedia.pyo", line 556, in AddItems
File "bpmedia.pyo", line 357, in _regenerateimagelist
File "wallpaper.pyo", line 121, in GetItemSizedBitmap
File "wxPython\image.pyo", line 255, in GetWidth
wxPyAssertionError: C++ assertion "wxAssertFailure" failed in
e:\Projects\wx2.4\src\common\image.cpp(829): invalid image
Variables by last 8 frames, innermost last
Frame __call__ in gui.pyo at line 73
self = <gui.Callback instance at 0x01D73F80>
args = (None, {'sync': {'wallpaper': 'OVERWRITE'}, 'wallpaper-index
d = {}
kwargs = {}
Frame OnDataGetPhoneResults in gui.pyo at line 731
self = <gui.MainWindow instance; proxy of C++ wxFrame instance at _
updwp = True
exception = None
results = {'sync': {'wallpaper': 'OVERWRITE'}, 'wallpaper-index': {150
v = 'OVERWRITE'
Frame populate in wallpaper.pyo at line 201
newitems = [{'origin': 'camera', 'name': 'V15Mar04-001.jpg', 'wp-index'
keys = [150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161,
k = 184
existing = []
dict = {'sync': {'wallpaper': 'OVERWRITE'}, 'wallpaper-index': {150
entry = {'origin': 'camera', 'name': 'V17Apr04-002.jpg'}
newentry = {'origin': 'camera', 'file': 'C:\\Documents and Settings\\mw
filename = 'C:\\Documents and Settings\\mwells\\My Documents\\bitpim\\w
self = <wallpaper.WallpaperView instance; proxy of C++ wxPanel inst
Frame SetItems in bpmedia.pyo at line 578
items = [{'origin': 'camera', 'name': 'V15Mar04-001.jpg', 'wp-index'
self = <wallpaper.WallpaperView instance; proxy of C++ wxPanel inst
Frame AddItems in bpmedia.pyo at line 556
items = [{'origin': 'camera', 'name': 'V15Mar04-001.jpg', 'wp-index'
self = <wallpaper.WallpaperView instance; proxy of C++ wxPanel inst
adict = {'origin': 'camera', 'file': 'C:\\Documents and Settings\\mw
key = 307
Frame _regenerateimagelist in bpmedia.pyo at line 357
stat = None
img = None
k = '__image_size'
imgsz = None
item = {'origin': 'camera', 'file': 'C:\\Documents and Settings\\mw
wxil = <wxPython.gdi.wxImageList instance; proxy of C++ wxImageList
il = [<wxPython.gdi.wxBitmapPtr instance; proxy of C++ wxBitmap i
key = 274
iconsz = (100, 100)
self = <wallpaper.WallpaperView instance; proxy of C++ wxPanel inst
Frame GetItemSizedBitmap in wallpaper.pyo at line 121
width = 100
self = <wallpaper.WallpaperView instance; proxy of C++ wxPanel inst
item = {'origin': 'camera', 'file': 'C:\\Documents and Settings\\mw
img = <wxPython.image.wxImage instance; proxy of C++ wxImage insta
height = 100
Frame GetWidth in wxPython\image.pyo at line 255
_kwargs = {}
self = <wxPython.image.wxImage instance; proxy of C++ wxImage insta
_args = ()
The Windows directory shows:
04/27/2004 11:32p 3,104 index.idx
04/27/2004 11:31p 146,949 MDM11Apr04-001.mp4
04/27/2004 11:31p 149,756 MDM16Mar04-001.mp4
04/27/2004 11:31p 146,270 MDM16Mar04-002.mp4
04/27/2004 11:31p 140,752 MDM17Apr04-001.mp4
04/27/2004 11:31p 143,303 MDM21Mar04-001.mp4
04/27/2004 11:31p 8,467 V03Apr04-001.jpg
04/27/2004 11:31p 49,664 V04Apr04-001.jpg
04/27/2004 11:31p 58,431 V11Apr04-001.jpg
04/27/2004 11:31p 51,668 V11Apr04-002.jpg
04/27/2004 11:31p 39,586 V15Mar04-001.jpg
04/27/2004 11:31p 44,935 V17Apr04-001.jpg
04/27/2004 11:31p 8,425 V17Apr04-002.jpg
04/27/2004 11:31p 61,198 V17Apr04-003.jpg
04/27/2004 11:31p 52,428 V17Apr04-004.jpg
04/27/2004 11:31p 40,660 V17Apr04-005.jpg
04/27/2004 11:31p 33,876 V18Apr04-001.jpg
04/27/2004 11:31p 52,309 V18Apr04-002.jpg
04/27/2004 11:31p 44,562 V18Apr04-003.jpg
04/27/2004 11:31p 40,020 V18Apr04-004.jpg
04/27/2004 11:31p 58,736 V18Apr04-005.jpg
04/27/2004 11:31p 45,524 V21Mar04-001.jpg
04/27/2004 11:31p 44,369 V23Apr04-001.jpg
04/27/2004 11:31p 45,641 V23Apr04-002.jpg
04/27/2004 11:31p 44,201 V26Mar04-001.jpg
04/27/2004 11:31p 33,180 V26Mar04-002.jpg
04/27/2004 11:31p 29,973 V27Mar04-001.jpg
04/27/2004 11:31p 49,836 V27Mar04-002.jpg
04/27/2004 11:31p 55,924 V27Mar04-003.jpg
04/27/2004 11:31p 9,130 V27Mar04-004.jpg
04/27/2004 11:31p 33,486 V27Mar04-005.jpg
04/27/2004 11:31p 60,754 V27Mar04-006.jpg
32 File(s) 1,827,117 bytes
|
|
From: Tom T. <to...@to...> - 2004-04-28 01:48:05
|
Here is the same error in Windows (XP):
An unexpected exception has occurred.
Please see the help for details on what to do.
Traceback (most recent call last):
File "gui.pyo", line 860, in OnEditSettings
File "guiwidgets.pyo", line 613, in ShowModal
File "guiwidgets.pyo", line 528, in setfromconfig
File "guiwidgets.pyo", line 448, in ApplyBitFlingSettings
File "bitflingscan.pyo", line 126, in decode
ValueError: invalid literal for int(): <u
Variables by last 8 frames, innermost last
Frame run in gui.pyo at line 349
args = (['C:\\Program Files\\BitPim\\bitpim.exe'],)
m = <gui.MainApp instance; proxy of C++ wxPyApp instance at _8e7
Frame MainLoop in wxPython\wx.pyo at line 1974
self = <gui.MainApp instance; proxy of C++ wxPyApp instance at _8e7
Frame MainLoop in wxPython\wx.pyo at line 92
_kwargs = {}
self = <gui.MainApp instance; proxy of C++ wxPyApp instance at _8e7
_args = ()
Frame OnEditSettings in gui.pyo at line 860
self = <gui.MainWindow instance; proxy of C++ wxFrame instance at _
_ = <wxPython.events.wxCommandEventPtr instance; proxy of C++ wx
Frame ShowModal in guiwidgets.pyo at line 613
self = <guiwidgets.ConfigDialog instance; proxy of C++ wxDialog ins
Frame setfromconfig in guiwidgets.pyo at line 528
self = <guiwidgets.ConfigDialog instance; proxy of C++ wxDialog ins
Frame ApplyBitFlingSettings in guiwidgets.pyo at line 448
self = <guiwidgets.ConfigDialog instance; proxy of C++ wxDialog ins
_ = None
Frame decode in bitflingscan.pyo at line 126
i = 0
res = []
str = '<unconfigured>'
"It's all about the ride..."
Tom Tracey
Puyallup, Washington
www.tomtracey.com
Proudly driving my "New" 1981 Yamaha Seca 750!
"I was made to last forever,
Though my body turn to sand,
My soul is in His hand..."
-=- Audio Adrenaline -=-
----- Original Message -----
From: "Stephen Wood" <sa...@ge...>
To: <bit...@li...>
Sent: Tuesday, April 27, 2004 4:51 PM
Subject: Re: [Bitpim-devel] 0.7-test9
> On Tue, 2004-04-27 at 18:29, Roger Binns wrote:
> > I have uploaded Windows and Linux builds to
> >
http://sf.net/project/showfiles.php?group_id=75211&package_id=76673&release_id=234373
> >
> > Please can you verify they work on your machines.
>
> On Linux RH9, if I first remove my .bitpim* files, startup bitpim, go to
> the Bitpim Settings panel and click the BitFling Enabled button, I get
> an exception. If I click on the BitFling settings first, click OK,
> there, then I don't get an exception when enabling.
>
> Will you be able to get the comment I made about Sanyo camera downloads
> in versionhistory.htd into the official build?
>
> Stephen
>
> An unexpected exception has occurred.
> Please see the help for details on what to do.
>
> Traceback (most recent call last):
> File "guiwidgets.py", line 448, in ApplyBitFlingSettings
> File "bitflingscan.py", line 126, in decode
> ValueError: invalid literal for int(): <u
>
> ...
>
> Frame decode in bitflingscan.py at line 126
> i = 0
> res = []
> str = '<unconfigured>'
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: Oracle 10g
> Get certified on the hottest thing ever to hit the market... Oracle 10g.
> Take an Oracle 10g class now, and we'll give you the exam FREE.
> http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
> _______________________________________________
> Bitpim-devel mailing list
> Bit...@li...
> https://lists.sourceforge.net/lists/listinfo/bitpim-devel
>
|
|
From: Tom T. <to...@to...> - 2004-04-28 00:38:28
|
MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAaCAJIAEggGyRnJv bTogIlRvbSBUcmFjZXkiIDx0b21AdG9tdHJhY2V5LmNvbT4NClRvOiA8Yml0cGltLWRldmVsQGxp c3RzLnNvdXJjZWZvcmdlLm5ldD4NClJlZmVyZW5jZXM6IDwwMDhhMDFjNDJjYTckMjE3ZmNhMDAk MzUwMWE4YzBAcm9nZXJzcXl2cjE0ZDM+IDwxMDgzMTA5ODc0LjE1Njk2LjEwLmNhbWVsQHN0ZXZl Pg0KU3ViamVjdDogUmU6IFtCaXRwaW0tZGV2ZWxdIDAuNy10ZXN0OQ0KRGF0ZTogVHVlLCAyNyBB cHIgMjAwNCAxNzozODoxMyAtMDcwMA0KQ29udGVudC1UeXBlOiB0ZXh0L3BsYWluOw0KCWNoYXJz ZXQ9Imlzby04ODU5LTEiDQpDb250ZW50LVRyYW5zZmVyLUVuY29kaW5nOiA3Yml0DQpYLVByaW9y aXR5OiAzDQpYLU1TTWFpbC1Qcmlvcml0eTogTm9ybWFsDQpYLU1haWxlcjogTWljcm9zb2Z0IE91 dGxvb2sgRXhwcmVzcyA2LjAwLjI4MDAuMTQwOQ0KDQoEgg6BSGVyZSBpcyB0aGUgc2FtZSBlcnJv ciBpbiBXaW5kb3dzIChYUCk6DQoNCkFuIHVuZXhwZWN0ZWQgZXhjZXB0aW9uIGhhcyBvY2N1cnJl ZC4NCg0KUGxlYXNlIHNlZSB0aGUgaGVscCBmb3IgZGV0YWlscyBvbiB3aGF0IHRvIGRvLg0KDQpU cmFjZWJhY2sgKG1vc3QgcmVjZW50IGNhbGwgbGFzdCk6DQoNCkZpbGUgImd1aS5weW8iLCBsaW5l IDg2MCwgaW4gT25FZGl0U2V0dGluZ3MNCg0KRmlsZSAiZ3Vpd2lkZ2V0cy5weW8iLCBsaW5lIDYx MywgaW4gU2hvd01vZGFsDQoNCkZpbGUgImd1aXdpZGdldHMucHlvIiwgbGluZSA1MjgsIGluIHNl dGZyb21jb25maWcNCg0KRmlsZSAiZ3Vpd2lkZ2V0cy5weW8iLCBsaW5lIDQ0OCwgaW4gQXBwbHlC aXRGbGluZ1NldHRpbmdzDQoNCkZpbGUgImJpdGZsaW5nc2Nhbi5weW8iLCBsaW5lIDEyNiwgaW4g ZGVjb2RlDQoNClZhbHVlRXJyb3I6IGludmFsaWQgbGl0ZXJhbCBmb3IgaW50KCk6IDx1DQoNClZh cmlhYmxlcyBieSBsYXN0IDggZnJhbWVzLCBpbm5lcm1vc3QgbGFzdA0KDQpGcmFtZSBydW4gaW4g Z3VpLnB5byBhdCBsaW5lIDM0OQ0KDQphcmdzID0gKFsnQzpcXFByb2dyYW0gRmlsZXNcXEJpdFBp bVxcYml0cGltLmV4ZSddLCkNCg0KbSA9IDxndWkuTWFpbkFwcCBpbnN0YW5jZTsgcHJveHkgb2Yg QysrIHd4UHlBcHAgaW5zdGFuY2UgYXQgXzhlNw0KDQpGcmFtZSBNYWluTG9vcCBpbiB3eFB5dGhv blx3eC5weW8gYXQgbGluZSAxOTc0DQoNCnNlbGYgPSA8Z3VpLk1haW5BcHAgaW5zdGFuY2U7IHBy b3h5IG9mIEMrKyB3eFB5QXBwIGluc3RhbmNlIGF0IF84ZTcNCg0KRnJhbWUgTWFpbkxvb3AgaW4g d3hQeXRob25cd3gucHlvIGF0IGxpbmUgOTINCg0KX2t3YXJncyA9IHt9DQoNCnNlbGYgPSA8Z3Vp Lk1haW5BcHAgaW5zdGFuY2U7IHByb3h5IG9mIEMrKyB3eFB5QXBwIGluc3RhbmNlIGF0IF84ZTcN Cg0KX2FyZ3MgPSAoKQ0KDQpGcmFtZSBPbkVkaXRTZXR0aW5ncyBpbiBndWkucHlvIGF0IGxpbmUg ODYwDQoNCnNlbGYgPSA8Z3VpLk1haW5XaW5kb3cgaW5zdGFuY2U7IHByb3h5IG9mIEMrKyB3eEZy YW1lIGluc3RhbmNlIGF0IF8NCg0KXyA9IDx3eFB5dGhvbi5ldmVudHMud3hDb21tYW5kRXZlbnRQ dHIgaW5zdGFuY2U7IHByb3h5IG9mIEMrKyB3eA0KDQpGcmFtZSBTaG93TW9kYWwgaW4gZ3Vpd2lk Z2V0cy5weW8gYXQgbGluZSA2MTMNCg0Kc2VsZiA9IDxndWl3aWRnZXRzLkNvbmZpZ0RpYWxvZyBp bnN0YW5jZTsgcHJveHkgb2YgQysrIHd4RGlhbG9nIGlucw0KDQpGcmFtZSBzZXRmcm9tY29uZmln IGluIGd1aXdpZGdldHMucHlvIGF0IGxpbmUgNTI4DQoNCnNlbGYgPSA8Z3Vpd2lkZ2V0cy5Db25m aWdEaWFsb2cgaW5zdGFuY2U7IHByb3h5IG9mIEMrKyB3eERpYWxvZyBpbnMNCg0KRnJhbWUgQXBw bHlCaXRGbGluZ1NldHRpbmdzIGluIGd1aXdpZGdldHMucHlvIGF0IGxpbmUgNDQ4DQoNCnNlbGYg PSA8Z3Vpd2lkZ2V0cy5Db25maWdEaWFsb2cgaW5zdGFuY2U7IHByb3h5IG9mIEMrKyB3eERpYWxv ZyBpbnMNCg0KXyA9IE5vbmUNCg0KRnJhbWUgZGVjb2RlIGluIGJpdGZsaW5nc2Nhbi5weW8gYXQg bGluZSAxMjYNCg0KaSA9IDANCg0KcmVzID0gW10NCg0Kc3RyID0gJzx1bmNvbmZpZ3VyZWQ+Jw0K DQoNCiJJdCdzIGFsbCBhYm91dCB0aGUgcmlkZS4uLiINClRvbSBUcmFjZXkNClB1eWFsbHVwLCBX YXNoaW5ndG9uDQp3d3cudG9tdHJhY2V5LmNvbQ0KUHJvdWRseSBkcml2aW5nIG15ICJOZXciIDE5 ODEgWWFtYWhhIFNlY2EgNzUwIQ0KDQoiSSB3YXMgbWFkZSB0byBsYXN0IGZvcmV2ZXIsDQogICAg ICBUaG91Z2ggbXkgYm9keSB0dXJuIHRvIHNhbmQsDQogICAgICAgICAgICBNeSBzb3VsIGlzIGlu IEhpcyBoYW5kLi4uIg0KICAgICAgICAgICAgICAgIC09LSBBdWRpbyBBZHJlbmFsaW5lIC09LQ0K LS0tLS0gT3JpZ2luYWwgTWVzc2FnZSAtLS0tLSANCkZyb206ICJTdGVwaGVuIFdvb2QiIDxzYXdA Z2VuaG9tZXBhZ2UuY29tPg0KVG86IDxiaXRwaW0tZGV2ZWxAbGlzdHMuc291cmNlZm9yZ2UubmV0 Pg0KU2VudDogVHVlc2RheSwgQXByaWwgMjcsIDIwMDQgNDo1MSBQTQ0KU3ViamVjdDogUmU6IFtC aXRwaW0tZGV2ZWxdIDAuNy10ZXN0OQ0KDQoNCj4gT24gVHVlLCAyMDA0LTA0LTI3IGF0IDE4OjI5 LCBSb2dlciBCaW5ucyB3cm90ZToNCj4gPiBJIGhhdmUgdXBsb2FkZWQgV2luZG93cyBhbmQgTGlu dXggYnVpbGRzIHRvDQo+ID4NCmh0dHA6Ly9zZi5uZXQvcHJvamVjdC9zaG93ZmlsZXMucGhwP2dy b3VwX2lkPTc1MjExJnBhY2thZ2VfaWQ9NzY2NzMmcmVsZWFzZV9pZD0yMzQzNzMNCj4gPg0KPiA+ IFBsZWFzZSBjYW4geW91IHZlcmlmeSB0aGV5IHdvcmsgb24geW91ciBtYWNoaW5lcy4NCj4NCj4g T24gTGludXggUkg5LCBpZiBJIGZpcnN0IHJlbW92ZSBteSAuYml0cGltKiBmaWxlcywgc3RhcnR1 cCBiaXRwaW0sIGdvIHRvDQo+IHRoZSBCaXRwaW0gU2V0dGluZ3MgcGFuZWwgYW5kIGNsaWNrIHRo ZSBCaXRGbGluZyBFbmFibGVkIGJ1dHRvbiwgSSBnZXQNCj4gYW4gZXhjZXB0aW9uLiAgSWYgSSBj bGljayBvbiB0aGUgQml0Rmxpbmcgc2V0dGluZ3MgZmlyc3QsIGNsaWNrIE9LLA0KPiB0aGVyZSwg dGhlbiBJIGRvbid0IGdldCBhbiBleGNlcHRpb24gd2hlbiBlbmFibGluZy4NCj4NCj4gV2lsbCB5 b3UgYmUgYWJsZSB0byBnZXQgdGhlIGNvbW1lbnQgSSBtYWRlIGFib3V0IFNhbnlvIGNhbWVyYSBk b3dubG9hZHMNCj4gaW4gdmVyc2lvbmhpc3RvcnkuaHRkIGludG8gdGhlIG9mZmljaWFsIGJ1aWxk Pw0KPg0KPiBTdGVwaGVuDQo+DQo+IEFuIHVuZXhwZWN0ZWQgZXhjZXB0aW9uIGhhcyBvY2N1cnJl ZC4NCj4gUGxlYXNlIHNlZSB0aGUgaGVscCBmb3IgZGV0YWlscyBvbiB3aGF0IHRvIGRvLg0KPg0K PiBUcmFjZWJhY2sgKG1vc3QgcmVjZW50IGNhbGwgbGFzdCk6DQo+ICAgRmlsZSAiZ3Vpd2lkZ2V0 cy5weSIsIGxpbmUgNDQ4LCBpbiBBcHBseUJpdEZsaW5nU2V0dGluZ3MNCj4gICBGaWxlICJiaXRm bGluZ3NjYW4ucHkiLCBsaW5lIDEyNiwgaW4gZGVjb2RlDQo+IFZhbHVlRXJyb3I6IGludmFsaWQg bGl0ZXJhbCBmb3IgaW50KCk6IDx1DQo+DQo+IC4uLg0KPg0KPiBGcmFtZSBkZWNvZGUgaW4gYml0 ZmxpbmdzY2FuLnB5IGF0IGxpbmUgMTI2DQo+ICAgICAgICAgICAgICAgaSA9ICAwDQo+ICAgICAg ICAgICAgIHJlcyA9ICBbXQ0KPiAgICAgICAgICAgICBzdHIgPSAgJzx1bmNvbmZpZ3VyZWQ+Jw0K Pg0KPg0KPg0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tLS0tLS0tDQo+IFRoaXMgU0YuTmV0IGVtYWlsIGlzIHNwb25zb3JlZCBieTogT3JhY2xlIDEw Zw0KPiBHZXQgY2VydGlmaWVkIG9uIHRoZSBob3R0ZXN0IHRoaW5nIGV2ZXIgdG8gaGl0IHRoZSBt YXJrZXQuLi4gT3JhY2xlIDEwZy4NCj4gVGFrZSBhbiBPcmFjbGUgMTBnIGNsYXNzIG5vdywgYW5k IHdlJ2xsIGdpdmUgeW91IHRoZSBleGFtIEZSRUUuDQo+IGh0dHA6Ly9hZHMub3Nkbi5jb20vP2Fk X2lkPTMxNDkmYWxsb2NfaWQ9ODE2NiZvcD1jbGljaw0KPiBfX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBCaXRwaW0tZGV2ZWwgbWFpbGluZyBsaXN0DQo+ IEJpdHBpbS1kZXZlbEBsaXN0cy5zb3VyY2Vmb3JnZS5uZXQNCj4gaHR0cHM6Ly9saXN0cy5zb3Vy Y2Vmb3JnZS5uZXQvbGlzdHMvbGlzdGluZm8vYml0cGltLWRldmVsDQo+DQoAAAAAAACgggjDMIIC SzCCAbSgAwIBAgIDDDO6MA0GCSqGSIb3DQEBBAUAMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJl ZW1haWwgSXNzdWluZyBDQTAeFw0wNDA0MjcwNTIyMjBaFw0wNTA0MjcwNTIyMjBaMEMxHzAdBgNV BAMTFlRoYXd0ZSBGcmVlbWFpbCBNZW1iZXIxIDAeBgkqhkiG9w0BCQEWEXRvbUB0b210cmFjZXku Y29tMIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDJNVM1GnSoUF2A/YjmXUQb7Bcc5zdTY2yR neDCPjthMBNQ+eQf2u3XE2K717h1P2OvY/Gj2y5Vks/cleAWCc6Fq3n5E1Oq4qhJj/kEDNizDEyt X2wVj3KSVOSgT9V2yr4OwVzxL2s5106KiXi9q7P7eFll+p+Fb8E74wdDZ+itDQIDAQABoy4wLDAc BgNVHREEFTATgRF0b21AdG9tdHJhY2V5LmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUA A4GBAJvYnyk4Dh4ZswCM984d9c81zTNAOdC5GwD3U4dStsLrayCuGu8SKj98TD5isvmld7pwvuUm jfAdDRZjk53ee0tph9YfAEWvb7yeVxOUXlfR1RQFImjA5a5bmcbzu80xg0M9Y5mvrtUJfuopQBPp bnSxL1onwatpSsXPXze2HdqwMIIDLTCCApagAwIBAgIBADANBgkqhkiG9w0BAQQFADCB0TELMAkG A1UEBhMCWkExFTATBgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYD VQQKExFUaGF3dGUgQ29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBE aXZpc2lvbjEkMCIGA1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcN AQkBFhxwZXJzb25hbC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTk2MDEwMTAwMDAwMFoXDTIwMTIz MTIzNTk1OVowgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcT CUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmlj YXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFp bCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTCBnzANBgkq hkiG9w0BAQEFAAOBjQAwgYkCgYEA1GnX1LCUZFtx6UfYDFG26nKRsIRefS0Nj3sS34UldSh0OkIs YyeflXtL734Zhx2G6qPduc6WZBrCFG5ErHzmj+hND3EfQDimAKOHePb5lIZererAXnbr2RSjXW56 fAylS1V/Bhkpf56aJtVquzgkCGqYx7Hao5iR/Xnb5VrEHLkCAwEAAaMTMBEwDwYDVR0TAQH/BAUw AwEB/zANBgkqhkiG9w0BAQQFAAOBgQDH7JJ+Tvj1lqVnYiqk8E0RYNBvjWBYYawmu1I1XAjPMPuo SpaKH2JCI4wXD/S6ZJwXrEcp352YXtJsYHFcoqzceePnbgBHH7UNKOgCneSa/RP0ptl8sfjcXyMm CZGAc9AUG95DqYMl8uacLxXK/qarigd1iwzdUYRr5PjRzneigTCCAz8wggKooAMCAQICAQ0wDQYJ KoZIhvcNAQEFBQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNV BAcTCUNhcGUgVG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRp ZmljYXRpb24gU2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVl bWFpbCBDQTErMCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0w MzA3MTcwMDAwMDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3 dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1h aWwgSXNzdWluZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjA dQRwnd/p/6Me7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn 8R+RNiQqE88r1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sC AwEAAaOBlDCBkTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9j cmwudGhhd3RlLmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjAp BgNVHREEIjAgpB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQAD gYEASIzRUIPqCy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6 GX6EsZkbAMUaC4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341Yh eILcIRk13iSx0x1G/11fZU8xggHMMIIByAIBATBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxU aGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJl ZW1haWwgSXNzdWluZyBDQQIDDDO6MAkGBSsOAwIaBQCggbowGAYJKoZIhvcNAQkDMQsGCSqGSIb3 DQEHATAcBgkqhkiG9w0BCQUxDxcNMDQwNDI4MDAzODEzWjAjBgkqhkiG9w0BCQQxFgQUfyMQg0Y8 c73dwAPIbZdSbrKxdKEwWwYJKoZIhvcNAQkPMU4wTDAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgIC AIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwBwYFKw4DAh0wDQYJKoZI hvcNAQEBBQAEgYAeiKepvkEdCtDORGw6FQSD4E0qAYbCOWE8BVCL2AcOiBjZbgVqn7CZ3LzMeRIh 328FjYBJ4oYf73jfbxq0cpQSocev3uyQTDCw7/Qsy+TWxBNiA4AxVhxPz1AfTlpGg1ZtgzZ0j1CZ A7rEMzsW3sc5ioEMB+XhP1RvKqZNkqpKAAAAAAAAAA== |
|
From: Stephen W. <sa...@ge...> - 2004-04-27 23:51:27
|
On Tue, 2004-04-27 at 18:29, Roger Binns wrote: > I have uploaded Windows and Linux builds to > http://sf.net/project/showfiles.php?group_id=75211&package_id=76673&release_id=234373 > > Please can you verify they work on your machines. On Linux RH9, if I first remove my .bitpim* files, startup bitpim, go to the Bitpim Settings panel and click the BitFling Enabled button, I get an exception. If I click on the BitFling settings first, click OK, there, then I don't get an exception when enabling. Will you be able to get the comment I made about Sanyo camera downloads in versionhistory.htd into the official build? Stephen An unexpected exception has occurred. Please see the help for details on what to do. Traceback (most recent call last): File "guiwidgets.py", line 448, in ApplyBitFlingSettings File "bitflingscan.py", line 126, in decode ValueError: invalid literal for int(): <u ... Frame decode in bitflingscan.py at line 126 i = 0 res = [] str = '<unconfigured>' |
|
From: Roger B. <ro...@ro...> - 2004-04-27 22:29:35
|
I have uploaded Windows and Linux builds to http://sf.net/project/showfiles.php?group_id=75211&package_id=76673&release_id=234373 Please can you verify they work on your machines. I had to do a considerable amount of figuring out packaging the encodings stuff, together with lots of other fun stuff. Also note that the Linux version is using Python 2.3 not the 2.2 of earlier builds. Please post to this list if they work or don't work for you. I believe everything will be fine. I will do the actual release tomorrow if no problems are reported. Roger |
|
From: Roger B. <ro...@ro...> - 2004-04-27 07:05:26
|
In one file, it turns out that Paramiko (the Python SSH2 implementation) that we use needs to process UTF8 data. The Python encodings are used to get that. It turns out that neither py2exe or cx_Freeze include the encodings package by default (it is fairly large and usage of it is almost impossible to detect). BundleBuilder may not include it either. Sadly it all falls over on Linux even after telling cx_Freeze to include encodings and encodings.utf_8. (The issues are to do with how Python was built and UCS2 vs UCS4). Consequently I am to use some seperate code to do conversion to and from UTF-8 rather than fight the encodings package. Plan B may be to upgrade to Python 2.3 on Redhat 9 instead and see if that fixes it. Anyway if anyone has any thoughts, or pointers to freely licensed Python UTF-8 code that has been debugged and tested, I would appreciate it. Anyway, it is my bedtime ... Roger |
|
From: Roger B. <ro...@ro...> - 2004-04-27 04:43:53
|
> In the interim (for this test release), I'm going to do some hacking. > I think it's better to use some default values The code did that until multiple phone models were introduced. At that point most people did not know that they needed to select a phone model as they never saw the dialog. I will mention this in the notes for the release. > P.S. I'll wait until you give the 'go ahead' to run the builds for > test-9. It is fine for Windows. Still testing on Linux. Roger |
|
From: Steven P. <n9...@n9...> - 2004-04-27 02:35:04
|
On Apr 26, 2004, at 9:22 PM, Roger Binns wrote: > Modal dialogs run their own nested event loops. This code shows it: I'll play with that and ask on the PythonMac lists... In the interim (for this test release), I'm going to do some hacking. I think it's better to use some default values than to have the user get a dialog they cannot interact with. It's far more confusing to them, IMHO. So, I'm hacking the startup to just set defaults and let the application continue it's launch. The user will have to be smart enough to actually go into the settings dialog and make the changes themselves. I'm only doing this for the Mac, not the other platforms. > I would love for that startup stuff to be simplified, and you are > currently looking at my best efforts :-) Well, you know this stuff inside and out better than I do, so I'm not promising much. I'll give it a good thinking through. > However it is a bit of late change to make now :-) Yeah, so for now I'm going to wimp out and just fake it on the Mac at initial (new user) launch time and hope they find the settings dialog. Not as user friendly, but it lets things load and doesn't give the user a blank/nonresponsive dialog and make them think the program isn't working. Steve P.S. I'll wait until you give the 'go ahead' to run the builds for test-9. |
|
From: Roger B. <ro...@ro...> - 2004-04-27 02:22:49
|
Steven Palm wrote:
> The problem with the initial config window coming up blank on MacOS
> (first run with no settings) seems (from my guesswork) to be related
> possibly to the dialog being thrown up in modal mode before the event
> loop is running... Is that a possibility?
Modal dialogs run their own nested event loops. This code shows it:
=====================
import wx
class FooDlg(wx.Dialog):
def __init__(self):
wx.Dialog.__init__(self, None, -1, "Just Testing")
vbs=wx.BoxSizer(wx.VERTICAL)
vbs.Add(self.CreateButtonSizer(wx.OK|wx.CANCEL|wx.HELP), 1, wx.ALIGN_CENTER|wx.ALL, 5)
self.SetSizer(vbs)
vbs.Fit(self)
app=wx.PySimpleApp()
foo=FooDlg()
foo.ShowModal()
=====================
> The dialog comes up blank, no
> controls are visible and the window widgets (close/minimize/maximize)
> don't work, or even have the usual rollover effects. Also, if you get
> an exception in this early stage the exception handling window has the
> same problems.
I wonder if it is to do with the parent of the dialog not being visible?
> I'm trying to monkey around with the startup code to simplify it and
> get the main loop up and running before the config dialog stuff is
> called just as a proof, but I'm not entirely sure at which point this
> happens.
I would love for that startup stuff to be simplified, and you are currently
looking at my best efforts :-)
The problem is that some of the tabs (wallpaper, ringtone etc) need to
know the pathname to where their data is stored when they get constructed.
Consequently that information has to be known before their construction.
That is why the code does the config stuff half way down the initialisation.
It also has to do fun stuff if the splash screen is still up.
I think a solution is for the various widgets to not load any data
when they get constructed. They get told to load stuff later anyway.
However it is a bit of late change to make now :-)
Roger
|
|
From: Roger B. <ro...@ro...> - 2004-04-27 02:11:54
|
Steven Palm wrote:
> The user has no way to call this. A "bundle" is a self-contained
> object to the MacOS Finder (although it's just a directory). In the
> bundle is a file "Info.plist" that tells the Finder what to launch when
> the bundle is "launched". There is no way to have two items in the
> bundle that would get launched.
That is bizarre. What happens when you have a suite like Office,
OpenOffice or Mozilla where there are multiple executables?
> If we are foregoing the need for a "clickable" launcher, then I can
> come up with some instructions on how to do it for the end-user through
> the command line.
For this release go with simplicity. BitFling is still somewhat rough
and the likely usage scenario is a developer running BitPim getting
someone with a particular phone running BitFling and walking them
through talking to each other.
> Getting a "clickable" bundle in the MacOS X Finder is a real PITA. :-)
Apparently. It could be worse. You could have Windows' Program
menu where apps install two things in a group. One runs the application
and the other uninstalls it. Given how often the latter is actually
used, and the consequences of clicking on it by accident, I have
yet to see the point.
I am just trying to fix one more minor issue and then everything should
be read for the build. (The tickbox for {en,dis}abling BitFling isn't
having much effect).
Roger
|
|
From: Steven P. <n9...@n9...> - 2004-04-27 01:49:28
|
Roger, Since I'm still trying to figure out all the ins and outs of the wx startup stuff... The problem with the initial config window coming up blank on MacOS (first run with no settings) seems (from my guesswork) to be related possibly to the dialog being thrown up in modal mode before the event loop is running... Is that a possibility? The dialog comes up blank, no controls are visible and the window widgets (close/minimize/maximize) don't work, or even have the usual rollover effects. Also, if you get an exception in this early stage the exception handling window has the same problems. I'm trying to monkey around with the startup code to simplify it and get the main loop up and running before the config dialog stuff is called just as a proof, but I'm not entirely sure at which point this happens. Anyway, any thoughts you have on this would be appreciated. Obviously this isn't an issue on Windows or Linux... Not sure if it's a MacOS "OS" issue or a wxMac issue. |
|
From: Steven P. <n9...@n9...> - 2004-04-27 01:44:49
|
On Apr 26, 2004, at 1:38 PM, Roger Binns wrote: > Steven Palm wrote: >> two in relation to each other, I can't think of a way to have a >> "bitfling" application bundle call items from the "bitpim" bundle. >> I'll >> give this some more thought. > > Can't you add a shell script that looks like this and put it in the > same directory of the bundle as the BitPim app object. The user has no way to call this. A "bundle" is a self-contained object to the MacOS Finder (although it's just a directory). In the bundle is a file "Info.plist" that tells the Finder what to launch when the bundle is "launched". There is no way to have two items in the bundle that would get launched. > For the moment it doesn't have to have an icon etc. It just needs to > be possible to start it in some way, even if that means using a > console. If we are foregoing the need for a "clickable" launcher, then I can come up with some instructions on how to do it for the end-user through the command line. Another alternative (ugly) is to require the user to put a clickable "bitfling" application bundle in the same directory as the "BitPim" bundle, and require that BitPim be named BitPim... Then the exec call in the shell script in the BitFling bundle could use relative directory paths to get into the resources of the BitPim bundle, possibly even using symlinks if needed to make it's bundle look "populated" with the right items. Getting a "clickable" bundle in the MacOS X Finder is a real PITA. :-) |
|
From: Peter D. <du...@hd...> - 2004-04-26 18:41:11
|
On Apr 26, 2004, at 1:31 PM, Steven Palm wrote: > This may be a bit more difficult on the Mac... Not sure. The whole > "bundle" that makes it possible to launch a Macintosh application with > the embedded libraries/etc requires that all the parts be in that > bundle... So the bitfling bundle would have to embed these all a > second time. Bad. Also, since you have no guarantee where they have > placed the two in relation to each other, I can't think of a way to > have a "bitfling" application bundle call items from the "bitpim" > bundle. I'll give this some more thought. What about using applescript? I mostly use the Mac as a unix system so I might be off base as to what you're up to. Peter Peter Dufault HD Associates, Inc. |
|
From: Roger B. <ro...@ro...> - 2004-04-26 18:38:04
|
Steven Palm wrote: > two in relation to each other, I can't think of a way to have a > "bitfling" application bundle call items from the "bitpim" bundle. I'll > give this some more thought. Can't you add a shell script that looks like this and put it in the same directory of the bundle as the BitPim app object. --------------------------------- #!/bin/sh dn=`dirname "$0"` exec "$dn/bitpim" bitfling --------------------------------- For the moment it doesn't have to have an icon etc. It just needs to be possible to start it in some way, even if that means using a console. > There is no way to run bitfling from within bitpim via a menu or > something? Just asking. ;-) It doesn't make sense. The intention is for it to sit in your tray and have no other user interface (unless you click on it). Consequently it needs to be started seperately and be possible to start automatically. Roger |
|
From: Steven P. <n9...@n9...> - 2004-04-26 17:31:16
|
On Apr 26, 2004, at 12:35 AM, Roger Binns wrote: > Please make sure all help changes are committed by 1pm PST Monday. > I hope to do the build sometime on Monday evening. I will plan on the same schedule for the Mac builds. > Please add an extra clickable application that runs "bitpim bitfling" > and name it BitFling. Don't worry about icons etc to. On Linux I > will be making a wrapper shell script that does that. On Windows just > a duplicate of the BitPim icon with more command line args supplied. This may be a bit more difficult on the Mac... Not sure. The whole "bundle" that makes it possible to launch a Macintosh application with the embedded libraries/etc requires that all the parts be in that bundle... So the bitfling bundle would have to embed these all a second time. Bad. Also, since you have no guarantee where they have placed the two in relation to each other, I can't think of a way to have a "bitfling" application bundle call items from the "bitpim" bundle. I'll give this some more thought. There is no way to run bitfling from within bitpim via a menu or something? Just asking. ;-) |
|
From: Roger B. <ro...@ro...> - 2004-04-26 06:06:09
|
Dale wrote: > How can I incorporate the TM520 code back into the development version, I > have added the three files but it doesn't show up under the setting drop > down. Look in guiwidgets. You may also want to read web/phonespec.html which describes how to add a new phone. Roger |
|
From: Roger B. <ro...@ro...> - 2004-04-26 05:35:13
|
Please make sure all help changes are committed by 1pm PST Monday. I hope to do the build sometime on Monday evening. Steven, Please add an extra clickable application that runs "bitpim bitfling" and name it BitFling. Don't worry about icons etc to. On Linux I will be making a wrapper shell script that does that. On Windows just a duplicate of the BitPim icon with more command line args supplied. Roger |
107 messages has been excluded from this view by a project administrator.
