On Mon, May 14, 2012 at 7:31 PM, Chase Douglas
wrote:
> Can we move the acceleration code to a library? The reason I ask is that
> we will want acceleration to feel the same whether the display server or
> a client wants to move objects.
Yep, I think this is a good point.
It avoids repeating the
On Wed, May 9, 2012 at 11:31 PM, Jonas Ådahl wrote:
> Touchpad related code has been rewritten and moved to its own file
> accessed by evdev via the dispatch interface.
>
> The various functionality implemented are anti-flicker (don't jumping
> around), smoother motions, touch detection, pointer a
On Wed, Feb 22, 2012 at 1:21 AM, Daniel Stone wrote:
> Because for a three-finger swipe, there
> will be a time when there's only one finger down, or two. At which
> point the client will say, 'ah yes, I'm interested in this!'. And
> then the third finger lands and you regret a terrible design
Some months ago, I have discussed the Wayland Crash Scenario and how windows
should reconnect to a newly started wayland either than being closed and
losing the open work.
I discussed with zhasha and daniels and below there is a resumé of some
points that may be useful:
...
wayland doesn't reall
On Fri, Feb 4, 2011 at 12:44 AM, Chris Morgan wrote:
> I noticed the TODO file but nothing jumped out and I figured I might
> as well just ask someone to pick for me a reasonable sized thing to
> work on as a beginner.
>
Add documentation,
work on input,
search for use cases and write either exp
Hi,
I was wondering whether we can find a better solution to the scenarios
where Wayland crashes.
You all know that for the X case, when it crashes, everything open is
lost, you need to re-login and you need to reopen your apps again.
Non-saved work will be lost.
Is it possible to change this for
