After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 656209 - Unable to maximise
Unable to maximise
Status: RESOLVED DUPLICATE of bug 643394
Product: pitivi
Classification: Other
Component: User interface
0.14
Other Linux
: Normal normal
: Git
Assigned To: Pitivi maintainers
Pitivi maintainers
Depends on:
Blocks:
 
 
Reported: 2011-08-09 12:09 UTC by Craig Barnes
Modified: 2011-08-22 15:27 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Craig Barnes 2011-08-09 12:09:22 UTC
When using Pitivi on my 10" netbook (1024x600 resolution), Pitivi's main window fails to maximise properly. When dragging the window up to maximise, the drop shadow disappears and the rounded top corners become square but the window itself just remains awkwardly in the centre of the screen.

Even in it's minimised state, the window is wider than 1024 pixels and thus hangs slightly off the right side of the screen. If I attempt to horizontally resize it, I can increase the width but not reduce it.

Obviously there is a minimum width in place that is interfering with transitioning to the maximised state.

I realise that using video editing software on a 10" netbook is a pretty small edge case but I just thought I'd put a bug report up here anyway.

Oddly, besides this rather annoying but minor issue, the software is actually quite fast and usable. I wouldn't have dreamed for such performance with other software even on a machine 2 or 3 times more powerful than a netbook. Just goes to show what utter bloatware most of the proprietary video editing software is.
Comment 1 Jean-François Fortin Tam 2011-08-22 15:27:40 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 643394 ***