maemo.org Bugzilla – Bug 4608
HildonBanner does not except NULL value for deprecated icon argument
Last modified: 2010-03-15 20:53:19 UTC
You need to log in before you can comment on or make changes to this bug.
SOFTWARE VERSION: N/A STEPS TO REPRODUCE THE PROBLEM: When creating a new Hildon Banner, pass None or NULL (depending on the programming language) as the second argument. EXPECTED OUTCOME: It will be ignored because Hildon 2.2 doesn't let developers specify icons. ACTUAL OUTCOME: It errors because argument 2 must be a string. REPRODUCIBILITY: always OTHER COMMENTS: Since the second argument is depreciated and only there to support software programmed for older Hildon versions, it should except None as a parameter (as that was the Default Icon). This behavior was observed using PyMaemo in the Fremantle Beta SDK, but assume it is also present in C, etc. User-Agent: Mozilla/5.0 (compatible; Konqueror/4.1; Linux) KHTML/4.1.4 (like Gecko)
So we talk about http://maemo.org/api_refs/5.0/beta/hildon/HildonBanner.html#hildon-banner-show-information and the other two functions to create a HildonBanner I guess. > ACTUAL OUTCOME: > It errors because argument 2 must be a string. For future reference, the exact errors message is always welcome. :-)
(In reply to comment #0) > When creating a new Hildon Banner, pass None or NULL (depending on > the programming language) as the second argument. > > EXPECTED OUTCOME: > It will be ignored because Hildon 2.2 doesn't let developers specify > icons. > > ACTUAL OUTCOME: > It errors because argument 2 must be a string. First of all, I'd like to apologize because I somehow overlooked this bug until now. I'm checking the HildonBanner C API and I can't see any method where you cannot pass NULL to create a banner. Currently the only deprecated parameter not being completely ignored is 'icon_name' in hildon_banner_show_information_with_markup(), but it accepts NULL as a valid value. So I'm closing this as FIXED. If you think this bug is still present feel free to add a comment. Thanks!
Setting explicit PR1.2 milestone (so it's clearer in which public release the fix will be available to users). Sorry for the bugmail noise (you can filter on this message).