Re: Old change in wallpaper index?

>
> 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?

2.  Sometimes pictures or ringers can not be asigned to contacts in BitPim.
> This could be because they are full photos from the phone, or because the
> phone protocol (at least to my understanding of it) lacks the ability to
> associate that particular file with the contact.  Can I make the index
> number negative to keep such files out of the BitPim menu for associating
> ringers and wallpaper with contacts?
>

There is a hack of unknown origin in the code for this. I had not intended
to fix it.
Currently only ringers with an origin of "ringers" or "builtin" are
assignable to contacts.
All wallpaper except those with an origin of "video" can be assigned.
The wallpaper index has real meaning on LG phones so it can't be changed.
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")


Simon