[BitPim-devel] Build time again

[Roger Binns]

I plan on doing the build Monday early on Monday evening (Pacific time).
Please remember to update the version history.

Roger

[Stephen Wood]

What is early? I have some quick (but important) cleanup for the
SPH-A620 and version history to write, but I won't be able to get to
it until about 10PM EST.

Stephen

Post by Roger Binns
I plan on doing the build Monday early on Monday evening (Pacific time).
Please remember to update the version history.
Roger

[Roger Binns]

Post by Stephen Wood
What is early? I have some quick (but important) cleanup for the
SPH-A620 and version history to write, but I won't be able to get to
it until about 10PM EST.

I am waiting for your all clear ...

Roger

[Stephen Wood]

All clear from me.

Post by Roger Binns

Post by Stephen Wood
What is early? I have some quick (but important) cleanup for the
SPH-A620 and version history to write, but I won't be able to get to
it until about 10PM EST.

I am waiting for your all clear ...

[Stephen Wood]

Post by Stephen Wood
All clear from me.

Whoops, forgot the version history. Just did that.

Stephen

[Roger Binns]

Post by Stephen Wood
Whoops, forgot the version history. Just did that.

I didn't see any change there. Anyway if you commit/correct it
I'll ensure the web version at least has the full details.

Roger

[John O'Shaughnessy]

Post by Roger Binns
I plan on doing the build Monday early on Monday evening (Pacific time).
Please remember to update the version history.

- No LG VX 6100 updates from me this week. I am not able to duplicate the
imported wallpaper sizing issue reported by two users. My only guess is
that they aren't expecting BitPim to resize and hold aspect ratio. The
behavior is as I expect on both Mac and Windows.

- Sadly, I confirmed that 20 camera images are all that are imported, even
if I bump up the count to 60, and modify the offsets. I started looking at
the protocol dumps to figure out the real index values, but didn't get very
far. FYI - On the Mac, the scroll bars often don't appear in the Protocol
Log window.

- I started to look at the request to increase the memo size beyond 32. It
appears that that value is not currently a variable, but is a numeric value.
I need to think more about the right way to deal with that.

- And, to top things off, I just started an rm -rf * in my home directory,
instead of in my ~/.bitpim-files directory... I caught it fairly early, but
time to get last nights backups... Thank goodness I back up regularly!


John

[Roger Binns]

Post by John O'Shaughnessy
- No LG VX 6100 updates from me this week.

Incidentally if you do have updates, they are preferred days in
advance rather than hours in advance :-)

Post by John O'Shaughnessy
far. FYI - On the Mac, the scroll bars often don't appear in the Protocol
Log window.

They always do for me. It is just a wx.TextCtrl. Sometimes people don't
realise that it needs scrolling.

Post by John O'Shaughnessy
- I started to look at the request to increase the memo size beyond 32. It
appears that that value is not currently a variable, but is a numeric value.
I need to think more about the right way to deal with that.

Work out the correct value. That sort of thing is easy to turn into a
variable.

Post by John O'Shaughnessy
- And, to top things off, I just started an rm -rf * in my home directory,
instead of in my ~/.bitpim-files directory... I caught it fairly early, but
time to get last nights backups... Thank goodness I back up regularly!

I use the rsync incremental backup mechanism on a seperate drive. Works
like a charm:

http://www.mikerubel.org/computers/rsync_snapshots/

Roger

[Roger Binns]

Post by Roger Binns

Post by John O'Shaughnessy
far. FYI - On the Mac, the scroll bars often don't appear in the Protocol
Log window.

They always do for me. It is just a wx.TextCtrl. Sometimes people don't
realise that it needs scrolling.

Of course what would happen to me shortly after sending this message :-)

It looks like the Mac wx.TextCtrl can't handle large amounts of text.
It gets *really* slow and eventually loses the vertical scrollbar.

Feel free to write an alternative as the text is read-only :-)

Roger