On Fri, 6 Mar 2015, Emmanuele Bassi wrote:
GNOME Shell *is* Mutter. The shell uses libmutter which provides ...
Thanks, Emmanuele. I assumed there was some type of subterfuge in effect
here.
Roger
___
gtk-app-devel-list mailing list
gtk-app-devel
Hi;
On Friday, 6 March 2015, Roger Davis wrote:
>
> I finally ran this down. The mutter window manager does indeed by default
> auto-maximize any newly mapped window larger than 0.8 of the 'usable screen
> area'. I think the latter means the space between gnome-shell's upper and
> lower toolbars
I finally ran this down. The mutter window manager does indeed by default
auto-maximize any newly mapped window larger than 0.8 of the 'usable
screen area'. I think the latter means the space between gnome-shell's
upper and lower toolbars, as I could never get anything more than about
0.75 of
On 03/06/2015 08:23 AM, Michael Cronenworth wrote:
> On 03/06/2015 08:52 AM, Michael Torrie wrote:
>> No, this is not quite what I am asking for. Capturing keyboard events
>> is fine, but I need the button to click visually, for feedback purposes.
>> Just like what happens if you define the cont
When using Glade to design a UI, I've noticed that the Button dialog has
an "Activatable/Actionable" section which includes an on/off "Use Action
Appearance" selection. This suggests that you might look into
GtkActionable and kin...
On 2015/03/06 07:55, Jim Charlton wrote:
> On 15-03-06 06:52 AM
On 15-03-06 06:52 AM, Michael Torrie wrote:
On 03/05/2015 09:31 PM, Jim Charlton wrote:
I presume you have a callback function connected to the button press
event. Just create code to intercept the keyboard event and go to a
callback function that sees what key was pressed and then calls the sa
On 03/06/2015 08:52 AM, Michael Torrie wrote:
No, this is not quite what I am asking for. Capturing keyboard events
is fine, but I need the button to click visually, for feedback purposes.
Just like what happens if you define the control key shortcut and press
that.
So the question is either,
On 03/05/2015 09:31 PM, Jim Charlton wrote:
> I presume you have a callback function connected to the button press
> event. Just create code to intercept the keyboard event and go to a
> callback function that sees what key was pressed and then calls the same
> function that would have been cal
