While that looks correct, I'm sure it breaks something. As the person who wrote that code, that choice was very intentional. Even though the protocol type is uint32_t, new_id arguments are always passed into libwayland as either a wl_proxy or wl_resource and that's what this code is designed to handle. --Jason
On Tue, Sep 30, 2014 at 8:45 AM, Jasper St. Pierre <[email protected]> wrote: > What is this trying to solve? > > On Mon, Aug 18, 2014 at 11:12 AM, Maks Naumov <[email protected]> wrote: > >> Signed-off-by: Maks Naumov <[email protected]> >> --- >> src/connection.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/src/connection.c b/src/connection.c >> index f292853..13e3a3e 100644 >> --- a/src/connection.c >> +++ b/src/connection.c >> @@ -492,7 +492,7 @@ wl_argument_from_va_list(const char *signature, union >> wl_argument *args, >> args[i].o = va_arg(ap, struct wl_object *); >> break; >> case 'n': >> - args[i].o = va_arg(ap, struct wl_object *); >> + args[i].n = va_arg(ap, uint32_t); >> break; >> case 'a': >> args[i].a = va_arg(ap, struct wl_array *); >> -- >> 1.9.1 >> >> >> >> _______________________________________________ >> wayland-devel mailing list >> [email protected] >> http://lists.freedesktop.org/mailman/listinfo/wayland-devel >> > > > > -- > Jasper > > _______________________________________________ > wayland-devel mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/wayland-devel > >
_______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
