Bug 4128 - Can not display "About", "Quit" and "Apply" line of window
Summary: Can not display "About", "Quit" and "Apply" line of window
Status: RESOLVED FIXED
Alias: None
Product: clawsker
Classification: Unclassified
Component: default (show other bugs)
Version: GIT
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2018-11-30 13:22 UTC by Numan Demirdöğen
Modified: 2018-11-30 14:33 UTC (History)
0 users

See Also:


Attachments
Adjust height (920 bytes, patch)
2018-11-30 14:22 UTC, Ricardo Mones
Details | Diff

Description Numan Demirdöğen 2018-11-30 13:22:13 UTC
Hi,

The laptop I am using has a 1366x768 pixels (361x203 millimeters) screen. In this laptop, I can not see a section of Clawsker's window where "Info", "Quit/Exit" and "Apply" buttons lay.

Steps to produce problem:
0. Use a GTK+3 theme
1. Clone Clawsker git repository and compile it after installing necessary dependencies
2. Start newly compiled Clawsker
3. Look for "Info" button :)

Clawsker version 1.2.0 has a window geometry of 587x700 pixels; but to be released 1.3.0 version has a window geometry of 950x753 pixels. Both version can be re-sized horizontally but not vertically.

I tried a couple of GTK+3 and GTK+2 themes. While using GTK+2 themes, window geometry of Clawsker let me see the hole window. On the other hand, while using GTK+3 themes, the problem above is occurring.
Comment 1 Ricardo Mones 2018-11-30 14:22:20 UTC
Created attachment 1938 [details]
Adjust height

Can you check if the attached patch fixes the problem for you?

During migrationg I tried to prevent it growing too much, but in a 1920x1200 screen these are small differences and harder to catch, thanks for reporting! ;-)
Comment 2 Numan Demirdöğen 2018-11-30 14:33:57 UTC
(In reply to comment #1)
> Created attachment 1938 [details]
> Adjust height
> 
> Can you check if the attached patch fixes the problem for you?
> 
> During migrationg I tried to prevent it growing too much, but in a 1920x1200
> screen these are small differences and harder to catch, thanks for
> reporting! ;-)

I confirm that the patch fixed the problem. Thank you for fixing it and fast response!

Note You need to log in before you can comment on or make changes to this bug.