maemo.org Bugzilla – Bug 3470
Control panel needs fullscreen mode
Last modified: 2009-10-22 07:57:26 UTC
You need to log in before you can comment on or make changes to this bug.
With the increasing number of third-party control panels, it'd make viewing the whole list somewhat easier if Control panel offered a fullscreen mode. Currently, pressing the fullscreen button in Control panel has no effect. User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US) AppleWebKit/523 (KHTML, like Gecko, Safari/523.10) OmniWeb/v621.0.99313
Created an attachment (id=830) [details] hildon-control-panel with fullscreen mode (patch) Though this is a 'easyfix' bug, I have added a patch for if someone need built the package with support for fullscreen.
dyerga: feel free to set the patch keyword. :-)
thanks yerga,add 2 simple function(one is supervised the current condition ,the other is replied the action) to the source.this bug can be solved~ actually,you can compare other application:-)
Only thing I can currently say is that this is a WONTFIX for Diablo...
Can't eve(In reply to comment #4) > Only thing I can currently say is that this is a WONTFIX for Diablo... > Can't even get them to apply a stupid page-long patch, eh? Yet more typically useless behavior from Nokia. Who do I need to email to get this fixed?
(In reply to comment #4) > Only thing I can currently say is that this is a WONTFIX for Diablo... Is this a "UI Specification" issue? There seems to be no technical reason why not, and the patch is provided. Are no more diablo releases timetabled? That'd be independent of actually accepting the patch.
No, not a UI spec issue. And I think there will be more Diablo updates published. It's just that the later you are in the cycle, the less less important stuff you accept...
(In reply to comment #7) > No, not a UI spec issue. And I think there will be more Diablo updates > published. It's just that the later you are in the cycle, the less less > important stuff you accept... > I'll reiterate what I said in bug #2639 here: I don't think it's unreasonable to expect that Nokia would spend 5 minutes to apply and ship community-provided patches (especially trivial ones) considering that many of these sorts of bugs have simply been ignored by Nokia until the opportunity to ship new fixes with Diablo has gone away. Not accepting these patches is really community-hostile, especially as the next generation of software is unlikely to run on current hardware (you guys really don't want to go into another 770 situation without a little compromise, especially after promising at least 2 rounds of support--and, no, Diablo does not count).
This is wontfix for Fremantle, due to reasons that will become obvious once Fremantle is released. Sorry I can't tell more at this time.
Marking patches of interest to Diablo (Maemo4) community updates, please excuse the noise.