maemo.org Bugzilla – Bug 5458
HildonEntry: Extra padding is undocumented.
Last modified: 2010-02-11 13:23:29 UTC
You need to
before you can comment on or make changes to this bug.
HildonEntry (and maybe other Hildon widgets) has padding/spacing around the
drawn parts of the widget, so that application developers get the correct
(according to the Maemo Master Layout Guide) spacing between widgets when, for
instance, placing them in a GtkVBox with 0 spacing.
This is unlike normal single-item GTK+ widgets, which
a) Require application developers to specify the spacing in their parent
b) Do not have useful defaults for spacing.
So this unexpected difference should be documented.
If I understand correctly what you mean, this is done at the theming layer. How
would this be best documented at the toolkit level, if it depends on the
theming engine and layout being used?
Oh, maybe it is. CCing someone who should know.
Even if it is theming, it seems to be happening in the standard theme for
Hildon::Entry but not for Gtk::Entry, though I don't 100% remember now what I
saw in my tests.
Maybe this implementation detail should be mentioned in the Maemo HIG, or one
of the other recently-released layout documents.
Yes, this is part of the themeing. It can be confusing when details like this
are not mentioned in the layout guides, which are generally not written from a
programmer's perspective. I doubt that the API documentation would be the right
place for it though, unless the documentation specifically refers to Maemo 5.
At the very least this should probably be mentioned in the UI spec.
The implementation also causes horrible artifacts when GtkButtons are put over
the top of images:
So, I'm going to have to do extra work to draw my own buttons (like Mauku,
Application Manager, Clock, ...).
(In reply to comment #3)
> I doubt that the API documentation would be the right place for it
> though, unless the documentation specifically refers to Maemo 5.
> At the very least this should probably be mentioned in the UI
So where should we reassign this bug?