Last active 2 years ago
View more

Recent activity

Re: [PATCH sxmo-dwm] grabkeys: Avoid missing events when a keysym maps to multiple keycodes 3 days ago

From Aren to ~mil/sxmo-devel

Merged, thanks

I amended it to also include the commit message from the upstream commit.

Re: [PATCH sxmo-utils] drop hook call_audio that hack on audio profile switch 7 days ago

From Aren to ~mil/sxmo-devel

I don't think we should get rid of the call audio hook, I remember
hearing users talking about using it to set up the volume the way they
liked it when starting a call.

Besides that, looks good to me

On Tue, Jun 04, 2024 at 10:46:37AM GMT, Willow Barraco wrote:
> It seems it has been fixed with 0.5.2. I've tested it for some weeks, and
> even just now, it continue to works.
> https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/156
> Signed-off-by: Willow Barraco <contact@willowbarraco.fr>
> ---
>  configs/default_hooks/sxmo_hook_call_audio.sh | 35 -------------------

[PATCH sxmo-utils] use git attributes to set version in makefile 8 days ago

From Aren Moynihan to ~mil/sxmo-devel

This adds configuration so that when "git archive" is run, it will
inject the current version into the makefile. This makes it so that we
don't have to do this manually, and packagers don't need to either.
 .gitattributes |  1 +
 Makefile       | 18 ++++++++++--------
 2 files changed, 11 insertions(+), 8 deletions(-)
 create mode 100644 .gitattributes

diff --git a/.gitattributes b/.gitattributes
new file mode 100644
index 0000000..71a5ad3
--- /dev/null
+++ b/.gitattributes
[message trimmed]

[PATH lisgd 4/4] use info macro for verbose logging a month ago

From Aren Moynihan to ~mil/sxmo-devel

This cleans up the code a bit, and will ensure we have a consistent log
 lisgd.c | 18 ++++++++----------
 1 file changed, 8 insertions(+), 10 deletions(-)

diff --git a/lisgd.c b/lisgd.c
index a5ab6b2..5b9e7e6 100644
--- a/lisgd.c
+++ b/lisgd.c
@@ -143,8 +143,7 @@ gesturecalculateswipe(double x0, double y0, double x1, double y1, int mindistanc
	degrees = 57.2957795130823209 * (t < 0 ? t + 6.2831853071795865 : t);
	dist = sqrt(pow(x1 - x0, 2) + pow(y1 - y0, 2));

[message trimmed]

[PATH lisgd 3/4] log touch events with timestamps a month ago

From Aren Moynihan to ~mil/sxmo-devel

I'm interested in analyzing how long gestures take to be recognized, and
how long the handler takes to process, so add log messages with this
 lisgd.c | 32 ++++++++++++++++++++++++++++++--
 1 file changed, 30 insertions(+), 2 deletions(-)

diff --git a/lisgd.c b/lisgd.c
index 13f0f18..a5ab6b2 100644
--- a/lisgd.c
+++ b/lisgd.c
@@ -85,6 +85,7 @@ Edge pendingedge;
Distance pendingdistance;
double xstart[MAXSLOTS], xend[MAXSLOTS], ystart[MAXSLOTS], yend[MAXSLOTS];
[message trimmed]

[PATH lisgd 2/4] add -F flag to execute all gestures as soon as they are matched a month ago

From Aren Moynihan to ~mil/sxmo-devel

This gives the system a head start on executing the gesture, at the cost
of some accuracy. This is a noticeable performance improvement, but it
requires adjusting how the gestures are used (to avoid incorrect
triggers). Put it behind a flag because of this.
My goal (we'll see if it's possible) is to optimize the common actions in sxmo
(such as opening the context menu or switching worksapces) to a point where the
action finishes before the touch up event.

 lisgd.1 |  6 ++++++
 lisgd.c | 24 +++++++++++++++++++++---
 2 files changed, 27 insertions(+), 3 deletions(-)

diff --git a/lisgd.1 b/lisgd.1
[message trimmed]

[PATH lisgd 1/4] spawn actions asyncronously a month ago

From Aren Moynihan to ~mil/sxmo-devel

This might help a little with the responsiveness of repeated gestures
such as volume and brightness in sxmo.

I wrote it so I can compare the time it takes to execute a gesture to
the time between touch-down and touch-up.
 lisgd.c | 19 +++++++++++++++++--
 1 file changed, 17 insertions(+), 2 deletions(-)

diff --git a/lisgd.c b/lisgd.c
index 921f5bc..b462446 100644
--- a/lisgd.c
+++ b/lisgd.c
@@ -8,6 +8,7 @@
[message trimmed]

Re: [PATCH sxmo-utils] Tentative to modularize inputhandler a month ago

From Aren to ~mil/sxmo-devel

On Mon, May 06, 2024 at 06:39:20PM GMT, Florent de Lamotte wrote:
> The idea is to split the big switch into sxmo_hook_inputhandler.sh into
> a script for each possible action. These script are stored in local and
> global inputhandler.d directories.

What do we gain from this? Is the idea that users can add actions for
apps and have to deal less with conflicts when upgrading?

On the topic of upgrading, will we want to keep inputhandler.d files up
to date with sxmo_migrate.sh?

I don't think this is necessarily a bad thing to do, but I'm not
convinced it's worth refactoring this much of the inputhandler. Would
something simpler, such as keeping the case statement in the root

Re: [PATCH sxmo-utils] contextmenu, firefox delete cookies+sitedata a month ago

From Aren to ~mil/sxmo-devel

On Tue, May 07, 2024 at 12:00:11AM GMT, hallo@magdesign.ch wrote:
> On 2024-05-05 16:56, Aren wrote:
> > On Sat, May 04, 2024 at 02:10:14PM +0200, Maarten van Gompel wrote:
> > > From: magdesign <hallo@magdesign.ch>
> > > 
> > > ---
> > >  configs/default_hooks/sxmo_hook_contextmenu.sh | 3 +++
> > >  1 file changed, 3 insertions(+)
> > > 
> > > diff --git a/configs/default_hooks/sxmo_hook_contextmenu.sh
> > > b/configs/default_hooks/sxmo_hook_contextmenu.sh
> > > index d3a72ca..86136ab 100755
> > > --- a/configs/default_hooks/sxmo_hook_contextmenu.sh
> > > +++ b/configs/default_hooks/sxmo_hook_contextmenu.sh