On Thu, Nov 3, 2011 at 2:59 PM, Benjamin Berg wrote:
> Palettes are still very broken in the sugar-toolkit-gtk3 branch. The
> problem is not very simple, and there is some unexpected trouble that we
> have not been able to figure out yet.
>
> For those that haven't heard any details, I'll try to e
Hello,
On Thu, 2011-11-03 at 23:54 +, Gary Martin wrote:
> This could only really work sanely from a design point of view if
> exposing a palette via a cursor hover/loiter also went away i.e.
> having to click outside somewhere to dismiss a palette that was auto
> triggered by a hovering actio
On Thu, 2011-11-03 at 23:54 +, Gary Martin wrote:
> Hi Benjamin,
>
> On 3 Nov 2011, at 20:59, Benjamin Berg wrote:
>
> > I am actually thinking about removing the popdown when the user leaves
> > the palette with the mouse.
>
> This could only really work sanely from a design point of view
Hi Benjamin,
On 3 Nov 2011, at 20:59, Benjamin Berg wrote:
> I am actually thinking about removing the popdown when the user leaves
> the palette with the mouse.
This could only really work sanely from a design point of view if exposing a
palette via a cursor hover/loiter also went away i.e. h
On 3 November 2011 20:59, Benjamin Berg wrote:
> I am actually thinking about removing the popdown when the user leaves
> the palette with the mouse.
Do you mean change how the palettes behave? Or is just an implementation detail?
Maro
___
Sugar-devel
Hello,
Palettes are still very broken in the sugar-toolkit-gtk3 branch. The
problem is not very simple, and there is some unexpected trouble that we
have not been able to figure out yet.
For those that haven't heard any details, I'll try to explain what is
going on here.
In GTK+ 3.x we are not a
6 matches
Mail list logo
