-libweston-desktop', 'main.c', dependencies :
[wayland_server, wayland_client, wayland_protocols, libinput,
libweston, pixman, xkbcommon, egl, libevdev, libweston_desktop])
How can I resolve my issue?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
On Thu, 2018-05-03 at 14:12 +0300, Pekka Paalanen wrote:
>
> what's the backtrace from gdb for that?
>
Is this any help?
#0 0x in ()
#1 0x7799c88c in weston_log (fmt=fmt@entry=0x779b6a7e
"Loading module '%s'\n") at libweston/log.c:75
#2 0x779a603c in west
calls.
>
That's fixed it, thank you!
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
running
How can I resolve this?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
I am attempting to write a simple test compositor using libweston.
Here is my code so far:
https://github.com/adlocode/test-libweston-desktop
What else do I need to do in order to get it to the point where something
appears on the screen, such as a rectangle of solid colour?
Regards
adlo
Thanks, this was very useful.
My compositor now works, but windows don't initially render until I click on my
compositor, though they render properly after that.
How can I resolve this?
Regards
adlo
> On 31 May 2018, at 10:05, Quentin Glidic
> wrote:
>
> Hi,
>
>>
r->surfaces_layer.view_list,
&pointer->focus->layer_link);
weston_view_geometry_dirty (shsurf->view);
weston_surface_damage (main_surface);
weston_desktop_surface_propagate_layer (shsurf->desktop_surface);
}
}
How can I resolve this?
Regards
adlo
__
Any ideas?
The rest of my code can be found at:
https://github.com/adlocode/test-libweston-desktop
Regards
adlo
On Tue, 2018-07-17 at 09:21 +0100, adlo wrote:
> I am writing a compositor using libweston. I am attempting to
> implement raising windows on click. It mostly works, but
when clicked.
Are there any possible solutions for this problem?
Regards
adlo
> On 27 Jul 2018, at 05:44, adlo wrote:
>
> Any ideas?
>
> The rest of my code can be found at:
> https://github.com/adlocode/test-libweston-desktop
>
> Regards
>
> adlo
>
>
I no longer seem to be able to find the wayland-wall repository on
GitHub. Just wondering what has happened to it?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland
f->view,
shsurf->saved_x, shsurf->saved_y);
if (shsurf->maximized)
set_maximized_position (shsurf);
}
An earlier version of the rest of my code can be found at:
https://github.com/adlocode/test-libweston-desktop/blob/master/shell.c
Regard
_valid)
weston_view_set_position(shsurf->view,
shsurf->saved_x, shsurf-
>saved_y);
shsurf->saved_position_valid = false;
}
Regards
adlo
On Mon, 2018-09-24 at 04:32 +0100, adlo wrote:
> I am writing a compositor using libweston. When unmaximiz
As far as I can tell my code looks the same as Weston's code. What might I be
doing differently that results in the windows not returning to their original
position?
Regards
adlo
> On 25 Sep 2018, at 04:41, adlo wrote:
>
> Here is some more code that I forgot to include:
&g
How do I run a GTK/GDK main loop from inside a libweston compositor? If I want
to use functions such as gdk_display_get_default () to get my compositor's
GdkDisplay, how do I guarantee that my compositor's display exists?
Regards
adlo
_
e child process to call functions and pass data to the parent
and vice versa?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
"xyz_implementation has initializer
but incomplete type" and "storage size of xyz_implementation isn't
known" How can I resolve this?
Also, what's the best way to include my private protocol's header
files, being as my code is in $(topdir)/src and the protocol headers
are in
to
do other than just specifying the location of the .xml files?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
On Fri, 2019-05-03 at 11:02 +0100, adlo wrote:
> > On 3 May 2019, at 10:20, Pekka Paalanen
> > wrote:
> >
> > your Makefile.am needs the rules to generate the headers and .c
> > files.
> >
>
> I tried copying an edited Makefile.am from the wayland-pro
> On 1 May 2019, at 10:34, Pekka Paalanen wrote:
>
> Hi adlo,
>
> it is all just the normal Wayland protocol exchange but with a new
> interface of your own design. I'm not sure if there is a really
> minimal example, but I'll list at least some.
>
>
It seems that the wayland-wall and weston-wall repositories have disappeared.
Any chance of them being reinstated?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland
I get the correct path to pass to weston_client_start()? How
does it find my object file?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
desktop);
I added a call to wl_global_create(). I also created a test client that calls
wl_registry_bind(), but my bind function doesn't seem to run, and
wl_registry_bind returns NULL. How can I resolve this?
(Is it OK to just pass the number 1 as the name parameter fo
On 9 May 2019, at 10:43, adlo wrote:
>> On 1 May 2019, at 10:34, Pekka Paalanen wrote:
>>
>> it is all just the normal Wayland protocol exchange but with a new
>> interface of your own design. I'm not sure if there is a really
>> minimal example, but I'l
> On 10 May 2019, at 08:48, adlo wrote:
>
> I put a call to weston_log() in my server-side bind function and then called
> wl_global_create() in my client. I was expecting to see my log entry printed
> to the screen but I got nothing.
>
> What could be going on?
I m
c,
char **argv)
{
display = wl_display_connect (NULL);
registry = wl_display_get_registry (display);
wl_registry_add_listener(registry, ®istry_listener, NULL);
wl_display_dispatch (display);
wl_display_dispatch (display);
return 0;
}
How can I fix this?
Regards
adlo
__
to add_idle() to
that, but that caused the client to segfault.
I tried putting wl_display_flush() wherever I could think of but to no
avail.
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
updated with information about this new window. However, the
surface_added function in shell.c doesn't know about the window switcher
protocol.
What is the best way to connect these two parts of the code?
Regards
adlo
___
wayland-devel mailing
> On 17 May 2019, at 09:10, Pekka Paalanen wrote:
>
> Hi,
>
> you forgot to use 'name'.
>
Thanks, that's fixed it!
> you should not include that in a
> client program.
>
Guess what I did :p
Regards
adlo
>
What do I pass as the "path" parameter to weston_client_start? How do I obtain
the value that I pass as "path"?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
> On 24 May 2017, at 19:41, Quentin Glidic
> wrote:
>
> On 5/24/17 8:37 PM, adlo wrote:
>> What I would like to do is get the desktop window so that I can display a
>> fake live image of the empty desktop as a background to my full-screen
>> window switcher
https://github.com/swaywm/wlr-protocols/blob/master/unstable/wlr-foreign-toplevel-management-unstable-v1.xml
>
Are there any examples of server-side implementations of
plasma-window-management.xml on libweston? Alternatively, are there any plain C
implementations of the same without all the
When switching tty, my compositor crashes with error messages such as
free (): invalid size Aborted (core dumped)
or
malloc (): invalid chunk size
when running on the DRM backend.
Here is my code:
https://github.com/adlocode/xfway/blob/master/src/main-wayland.c
https://github.com/adlocode/xf
On Tue, 2019-05-28 at 13:38 -0400, Adam Jackson wrote:
> On Tue, 2019-05-28 at 08:26 +0100, adlo wrote:
> > When switching tty, my compositor crashes with error messages such
> > as
> >
> > free (): invalid size Aborted (core dumped)
> > or
> > malloc
> On 29 May 2019, at 03:53, Matteo Valdina wrote:
>
>
> As valgrind pointing out at shell.c line 982
>
> shell = zalloc (sizeof (shell));
>
> Here you are allocating the pointer size not the structure size. You probably
> want type Shell.
>
This reduces the amount of crashing, but does not
On Wed, 2019-05-29 at 08:19 -0500, Matteo Valdina wrote:
> Re-iterate the process.Run valgrind, read the log, search for bugs.
> Until valgrind run smoothly.
>
> Best
>
> On Wed, May 29, 2019, 02:32 adlo wrote:
> > On 29 May 2019, at 03:53, Matteo Valdina
> >
On Thu, 2019-05-30 at 13:39 +0300, Pekka Paalanen wrote:
> On Thu, 30 May 2019 00:50:32 +0100
> adlo wrote:
>
> > Also, there are lots of "Invalid writes of size 8", but a lot of
> > them
> > don't seem to originate from functions in my program, but
On Fri, 2019-05-31 at 01:22 +0100, adlo wrote:
> On Thu, 2019-05-30 at 13:39 +0300, Pekka Paalanen wrote:
> >
> > Hi,
> >
> > as always, look at the very first problem reported. Other problems
> > may be fallout from the first one, so fix the first one, and
>
> On 1 May 2019, at 10:34, Pekka Paalanen wrote:
>
> On Wed, 1 May 2019 03:24:04 +0100
> adlo wrote:
>
> it is all just the normal Wayland protocol exchange but with a new
> interface of your own design. I'm not sure if there is a really
> minimal example, but I&#x
was forked.
>
Is it required that the helper client be a separate binary that must be
launched through a path? Is it possible for the client to just be a function in
my main program?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
objects such as
weston_surface, weston_desktop_surface. How are these two connected?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
> On 22 May 2019, at 21:36, Ilia Bozhinov wrote:
>
> If you have a panel/any UI elements, then you most probably have a protocol
> to communicate that the UI element surface is a special surface. You could
> then just extend this protocol so that you specify Z-ordering of these
> surfaces, and
level protocol, which can be used for window
management functions, and the wlr-layer-shell protocol, which can be used for
creating panels etc.
At the moment it's little more than a Weston clone with some wlroots support,
but there you go.
What do you think?
Reg
t of Xfce,
and I would be best served by doing my own thing separate from Xfce.
Regards
adlo
> On 27 Jun 2019, at 19:30, adlo wrote:
>
> xfway is a Wayland compositor inspired by xfwm4:
>
> https://github.com/adlocode/xfway
>
> I'm not sure if this is an actua
Hi
Does xkbcommon have a function to convert a keysym to a keycode?
Also, what keycodes does Weston use? It seems that in libweston, KEY_TAB is
assigned the number 15. Is this a real keycode? Is this a standard keycode? Is
it used in xkbcommon or anything like that?
Regards
adlo
Basically the program I’m working on was originally designed for X11, and I’m
trying to adapt it to Wayland. I’m trying to find an equivalent to
XKeysymToKeycode().
> it doesn't, but if you look at xkbcli how-to-type and it's source
> (tools/how-to-type.c) that's the closest approximation.
What
Does xkbcommon have modifier masks, like that used in the “state” field of
XKeyEvent?
> On 4 Dec 2021, at 08:34, adlo wrote:
>
> Basically the program I’m working on was originally designed for X11, and
> I’m trying to adapt it to Wayland. I’m trying to find an e
> On 5 Dec 2021, at 05:15, Peter Hutterer wrote:
>
> please look at the source, it's not a huge program.
I have looked at the source, it’s just that I can’t see anything that’s
directly related to what I’m trying to do. It calls
xkb_keymap_key_get_mods_for_level(), which seems to be related to
Hi
I’ve backported labwc to wlroots 0.14:
https://github.com/adlocode/labwc/tree/wlroots-0.14-backports
It might be useful when developing compositors for non-bleeding-edge distros,
perhaps.
Regards
adlo
xfway now supports the alt-tab switcher:
https://github.com/adlocode/xfwm4/tree/wayland
Regards
adlo
xfway is a Wayland compositor inspired by xfwm4.
xfway is now able to run xfwm4’s alt-tab window switcher code.
The current developments are at the adlocode/xfwm4 repo, the xfway repo is
currently outdated.
Regards
adlo
> On 14 Jan 2022, at 03:27, adlo wrote:
>
> xfway now sup
code/xfwm4/tree/wlroots
Regards
adlo
the two repos to
diverge in some ways but still keep up with the changes from the other one.
I ended up with two repos because I’m not sure if I want this to be an
independent project or an official part of Xfce.
Regards
adlo
> On 16 Jul 2022, at 00:01, Alex wrote:
>
> Hi Adlo,
>
Begin forwarded message:
> From: adlo
> Date: 17 July 2022 at 02:54:11 BST
> To: Xfce development list
> Subject: Re: xfway: added support for alt-tab switcher
>
>
>>
>> On 15 Jan 2022, at 14:02, Alex wrote:
>>
>> Hi adlo,
>>
>
modifier?
Regards
adlo
> On 5 Dec 2021, at 23:14, adlo wrote:
>
>
>>
>> On 5 Dec 2021, at 05:15, Peter Hutterer wrote:
>>
>> please look at the source, it's not a huge program.
>
> I have looked at the source, it’s just that I can’t see any
How are return values specified in the Wayland XML specification?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
; that accumulates. Therefore one should reconsider if a roundtrip is
> really necessary, or if things could be designed to be asynchronous
> instead.
For example, getting a list of windows and returning it as an array. How would
this be done? How are arrays represented in Way
bnails? How does your protocol compare to KDE's
org_kde_plasma_windowmanagement?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
are sent by an interface or received by
it?
How do you link the request with its corresponding response event? If the
client sends a get_window request, how does the server know how to respond to
it? Do they both need to be specified in the XML?
Regards
adlo
Do any compositors support this protocol?
Regards
adlo
> On 15 May 2017, at 14:27, Quentin Glidic
> wrote:
>
> On 5/15/17 3:13 PM, adlo wrote:
>>> On 15 May 2017, at 10:52, Quentin Glidic
>>> wrote:
>>> If you are writing/porting a window switcher,
ktop, panel, or normal window, or whether it is skip tasklist,
skip pager etc?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
) == WNCK_WINDOW_DESKTOP)
{
return win;
}
}
return NULL;
}
How could I do this?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/
I have built Weston from source. When trying to run it in a nested window
on GNOME Wayland, it gives me the error message "Failed to load module:
/lib/libweston-3/wayland-backend.so: cannot open shared object file: No
such file or directory"
How can I resolve this?
Reg
How do I compile wayhouse against my locally compiled libweston?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
On Tue, May 30, 2017 at 12:30 AM, adlo wrote:
> I have built Weston from source. When trying to run it in a nested window
> on GNOME Wayland, it gives me the error message "Failed to load module:
> /lib/libweston-3/wayland-backend.so: cannot open shared object file: No
> such
On Tue, May 30, 2017 at 2:24 AM, adlo wrote:
> How do I compile wayhouse against my locally compiled libweston?
>
Can I compile wayhouse against Fedora 25 stock libweston instead of a git
version? Is Fedora's libweston up-to-date enough for wayhouse?
Re
Is libweston 1.0 good enough for writing a compositor? Are there any tutorials
or simple examples for writing a compositor using any version of libweston?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https
On Wed, May 31, 2017 at 1:54 PM, Quentin Glidic <
sardemff7+wayl...@sardemff7.net> wrote:
> On 5/31/17 2:37 PM, adlo wrote:
>
>> Is libweston 1.0 good enough for writing a compositor?
>>
>
> Yes, but each major version is adding or changing API to make it s
hat. :-)
How do I initialise a simple compositor using libweston-desktop?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
On Fri, Jun 2, 2017 at 1:51 AM, adlo wrote:
> How do I write a program that spawns a simple compositor instance on a
> nested Wayland window using libweston-desktop and the Wayland-on-Wayland
> backend? What are the absolute basics needed to get something on the screen
> using libwe
d shortcuts are now kinda configurable? Though it currently only works
for the alt-tab switcher, and the only modifier key it recognises is Alt.
Git repository:
https://github.com/adlocode/xfwm4/tree/wlroots
Regards
adlo
/wayland
Regards
adlo
be removed as afaik you can't do GTK
server side? I don't necessarily want to make it one binary.
How does mutter manage to be one binary? On X11, the window manager is a client
but on Wayland the window manager is a server, so the directionality of X11 and
Wayland is the complete op
you ended up with
either the GTK bit running, or the compositor, but not both. I know you can do
cairo server-side, because that's just drawing pixels on the screen, but I
didn't think you could do GTK.
Regards
adlo
-2
Regards
adlo
rking if I make the Client
struct smaller. So I think maybe it's got something to do with the size of the
struct.
What's going on?
Regards
adlo
> On 31 Mar 2023, at 12:44, adlo wrote:
> I have rewritten my Wayland port of xfwm4 for the third or fourth time.
>
> I kept a
Correction: the View struct is in src/wayland/output.h, not view.h
> On 4 Apr 2023, at 08:07, adlo wrote:
>
> If I use my View struct (src/wayland/view.h), everything is fine. But if I
> try to copy the contents of the View struct into the Client struct
> (src/client.h) and
and-2 branch to wayland and renamed my
old wayland branch to wayland-old.
My latest code can now be found here:
https://github.com/adlocode/xfwm4/tree/wayland
Regards
adlo
be fairly easy in theory. From your client perspective it would
> be a little like a special sub-surface whose content magically just
> appears on screen.
If I wanted to try writing something like this as a Weston extension for
testing purposes, how could I get the window's surface?
Reg
dow previews/thumbnails would be handled in the compositor/shell.
Does mutter support pixman 2D software rendering? I believe that xfwm4 supports
this through XRender.
Regards
adlo
___
wayland-devel mailing list
wayland-devel@list
a protocol object interface) for referring to windows, and
> communicate any metadata you may need with it.
What is Weston's internal representation of a window's surface? What parts of
the code are most relevant to these kinds of things?
Regards
adlo
__
and Security Modules (libwsm)? In what ways does this not solve
the security issues of privileged interfaces?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
with privileged interfaces?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
dows
in a similar way to libwnck? Does xdg-shell expose the inner workings of the
compositor thus making it unsuitable?
Regards
adlo
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-devel
interface using a privileged
handle without any security issues?
Also, Derek's reply mentions a "common module framework". How is this different
from a Wayland protocol, and what are its advantages?
Regards
adlo
> On 1 Jun 2016, at 09:00, Pekka Paalanen wrote:
>
> O
Any ideas about this?
> On 7 Jun 2016, at 16:04, adlo wrote:
>
> There are many other protocols that may require handles to windows. It may
> make sense for them to all use the same handle protocol. Of course, all of
> these different protocols would require different leve
car". you can still do it, but you're now talking about a tiny subset of
> users that want things that way.
>
> so the case of no DE is niche in X, and effectively non-existent in wayland
> (because you *need* a compositor).
What is the minimum setup that is possible with Way
Is it possible to have a callback function for *all* key events using
weston_compositor_add_key_binding () in libweston-desktop?
Are the modifiers passed to the callback function, or only the keycode?
Regards
adlo
88 matches
Mail list logo
