Re: Old change in wallpaper index?

On 5/3/06, Simon C <[email protected]> wrote:
>
> 1.  Many phones will often have two copies of a photograph.  One that is
> > full size and one that is resized and assignable to contacts.  Sometimes
> > these will have the same name and I resort to hackery in the driver to make
> > sure that they get different names in BitPim.  (So that one or the other
> > doesn't get clobbered.)  Is there something we can do so that the driver
> > does not need to worry about name collisions.
> >
>
> This will change in the new code. The name of the wallpaper will only need
> to be unique within the origin it is in. So you could have a "camera_raw"
> origin and a "camera_assignable" origin with images with the same name. Will
> this work for the scenario you describe?
>
It will work great.  Perhaps we can make origin names like "camera_fullsize"
and "camera_thumbnail" or such to make it clear which is the better photo.
Roughly, the phones seem to call the original photos "Review" and the
thumbnails "Saved to Phone", masking the fact that the "Saved" photos no
longer have the original resolution.

Also, the reduced photos are not necessarily assignable (through BitPim)
because I havn't figured out how to assign them on the Sprint Sanyo and
Samsung phones I have worked with.  (But I just came across a comment by Joe
from ages ago that described how he did assignments for his Verizon Samsung
that I need to try with my Sprint one.)



> How about adding a couple of tuples to the phone profile of
> wallpaper_origin_exclude_from_contacts("raw_camera", "video", "mms")
> ringer_origin_exclude_from_contacts("sounds", "mms", "mp3s")
>

Something like that would work and be better than any hack I would come up
with.

Stephen