> gnome-shell-list-requ...@gnome.org
>
> You can reach the person managing the list at
> gnome-shell-list-ow...@gnome.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of gnome-shell-list digest...&qu
Hi,
A small update:
On 13 Sep 2013 01:35, "Michele" wrote:
>
> Hi,
>
> Whilst trying to keep updated the dash-to-dock extension for Gnome-Shell
3.9 I stumble on the removing of the affectsInputRegion parameter. I'm
wondering if the solution suggested by Vadim - using the private method
layoutMa
e.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of gnome-shell-list digest..."
>
>
>Today's Topics:
>
> 1. Re: GS 3.9 affectsInputRegion (Michele)
> 2. Re: Fedora 19 and Gnome 3.8 (Andrew Douglas Pitonyak)
>
Hi,
Whilst trying to keep updated the dash-to-dock extension for Gnome-Shell
3.9 I stumble on the removing of the affectsInputRegion parameter. I'm
wondering if the solution suggested by Vadim - using the private method
layoutManager._trackActor instead of layoutManager.trackChrome to force the
Hi Jasper,
Yes, I kind of do. The parent actor is GenericContainer, and its
position is fixed. Its children are placed inside the parent at some
positions. I just searched through my installed extensions and found out
that, for example, Dash to Dock uses similar concept to position the
dash: there
Do you really need the parent-child relationship?
On Tue, Jul 9, 2013 at 4:45 PM, Vadim wrote:
> Hi everyone,
>
> I have a question about GS 3.9. One of the commits removes the
> affectsInputRegion parameter. I know there were some special reasons for
> that, and a lot of underlying C code has
ne so it is more specific
> than "Re: Contents of gnome-shell-list digest..."
>
>
> Today's Topics:
>
>1. GS 3.9 affectsInputRegion (Vadim)
>
>
> --
>
> Message: 1
&g
Hi everyone,
I have a question about GS 3.9. One of the commits removes the
affectsInputRegion parameter. I know there were some special reasons for
that, and a lot of underlying C code has changed.
Now, suppose I have an actor A that takes some space but I want it to be
transparent for all event
