maemo.org Bugzilla – Full Text Bug Listing |
Summary: | GtkMessageDialog text gets cripplet in portrait mode | ||
---|---|---|---|
Product: | [Maemo Official Platform] Desktop platform | Reporter: | Cornelius Hald <hald> |
Component: | gtk | Assignee: | unassigned <nobody> |
Status: | RESOLVED WONTFIX | QA Contact: | gtk-bugs |
Severity: | normal | ||
Priority: | Medium | CC: | agarcia, andre_klapper, eero.tamminen, jamie.bennett, tim |
Version: | 5.0-beta | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | Maemo | ||
Attachments: | Crippled GtkMessageDialog |
Created an attachment (id=1212) [details] Crippled GtkMessageDialog The complete text on this dialog would be: <dialog> Really delete this note? If you delete a note it is permanently lost. </dialog>
> Then maybe I should file a new bug: "Portrait mode not supported!" Well, the thing is that Fremantle is meant to be used mostly in landscape mode. There's support for portrait mode as well, but it was introduced for a few specific use cases rather than meant for all programs (in fact, apps have to explicitly indicate that they support portrait mode). It's true that not all apps are going to look nice when changed to portrait mode without changes, and I don't think it can (or should) be done in a generic way. Some widgets (e.g. HildonAppMenu) are aware of portrait mode, but most of them are not (and as I've just said, I don't think there's a good generic solution for most widgets). I admit that some widgets might have some extra support. However, having full-fledged support for portrait mode as a goal for Fremantle doesn't only involve changes in the code, but also a lot of effort on design, testing, etc. As our resources are limited, we try to focus first on other important parts of the platform that also need our work. Of course we could have made the portrait API secret just to solve our internal needs, but do you really think it would have been better? :)
I have filed bug 4648 about the portrait mode documentation not being verbose and explicit enough. This bug here is unfortunately WONTFIX, as mentioned.