I'm holding an open beta until September 30th. The one feature that isn't present at this time is the safelist bar. Changes were made in BlackBerry 7 that prevent it from showing up so I'm working on having this fixed in an update.
5.0+ only. Let me know if you run into any issues.
Hey JC,
Looks like I'm the odd man out on this one as I only used the "Safelist Bar" and never used the "All" mode on my 9780. So, I gather from your OP, since you will be adding this later after working out some OS7 issues, that there will be only one build as opposed to several OS builds. I guess I will have to get used to the "All mode" in the mean time then.
@Diegonei... The "Remove from Menu" item was present in the previous version. At least for v1.3.16. This is for users like myself who choose to accept the additional images on a case by case basis. In the previous version it could be done via the "Safelist Bar", via the BB menu key list, or both. This option just allows it to be removed from the BB menu if you so choose.
Also, the backup/restore never worked for me in the previous version as well, so I am eager to test this out myself.
Thanks JC,
Updates are always welcome...
Brad
EDIT: I just downloaded it and I still have a safelist bar option listed (Yay), but I don't know if it works for OS6 still. Let me send an email to myself as see. Let you know in a minute or two.
EDIT: Nah... No safelist bar for OS6. I love that red bar... But, I'm patient... lol.
Some "space" issue ... when i type max size for attachment download greater that 999, there is not enough "space" and you see the fourth digit at the next row. It doesn't affect the functionality of the app though.
This doesn't seem to be working on my Torch 9850. I have it set to download all and no safe list, yet I still have to do the get images thing from the menu.
For people on OS versions lower than 7.0.0.300, I will check and get back to you guys. For people on .353 is it working OK without the bar or still not working?
A lot of changes were made between OS versions so I'm trying to find workarounds for those changes. Stay tuned.