Github messages for voidlinux
 help / color / mirror / Atom feed
From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Blender 3D - Wayland Support 
Date: Tue, 19 Jul 2022 00:30:48 +0200	[thread overview]
Message-ID: <20220718223048.w3fc35UHFUfMH66fcZcYSYswecim5mzCKb49zwhB9-g@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38128@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 768 bytes --]

New comment by classabbyamp on void-packages repository

https://github.com/void-linux/void-packages/issues/38128#issuecomment-1188388006

Comment:
based on how that issue describes the current state of blender, it seems that this might cause issues/weird behaviour on X:

![image](https://user-images.githubusercontent.com/5366828/179627441-5c8e7650-c6f7-4dd0-8213-98e9ab6eca9c.png)

first line is what we have now, second line is not possible for void's package, third line seems like the way to go.

IMO, I think we can't do much until the proposed solution is implemented, allowing us to enable both compile-time flags and allowing wayland users to select it at runtime.

Maybe someone who uses blender and knows more about it can shed some light on this.

  parent reply	other threads:[~2022-07-18 22:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 13:11 [ISSUE] " jdnumm
2022-07-18 22:30 ` classabbyamp
2022-07-18 22:30 ` classabbyamp [this message]
2022-07-18 22:31 ` classabbyamp
2022-10-18  2:14 ` github-actions
2023-01-05  2:00 ` NiseVoid
2023-03-14 17:08 ` mhmdanas
2023-06-13  1:59 ` github-actions
2023-09-12  1:44 ` github-actions
2023-09-26  1:45 ` [ISSUE] [CLOSED] " github-actions
2024-01-07 15:04 ` Channpyae
2024-01-11 15:46 ` JetpackJackson
2024-01-11 16:54 ` Channpyae

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220718223048.w3fc35UHFUfMH66fcZcYSYswecim5mzCKb49zwhB9-g@z \
    --to=classabbyamp@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).