On Tue, 01 Dec 2015 14:27:40 +0900
Hyungwon Hwang wrote:
> Hello all,
>
> Reading the mail thread, I tried to figure out the problem by myself.
> Until now, I couldn't find any reason to make fullscreen application
> totally opaque. As I found in git history, in my opinion, the author
> of fulls
Hello all,
Reading the mail thread, I tried to figure out the problem by myself.
Until now, I couldn't find any reason to make fullscreen application
totally opaque. As I found in git history, in my opinion, the author
of fullscreen implementation just thought that fullscreen has black
surface beh
On Thu, 26 Nov 2015 15:33:24 +0800
zou lan wrote:
> Hi Pekka
>
> I have another question about the fullscreen NULL buffer display black
> surface. Why the fullscreen App call hide(commit Null buffer), then start
> another App, only the fullscreen App can show normally? Is the normal
> screen Ap
Hi Pekka
I have another question about the fullscreen NULL buffer display black
surface. Why the fullscreen App call hide(commit Null buffer), then start
another App, only the fullscreen App can show normally? Is the normal
screen App's layer below on the black surface?
Best Regards
Nancy
2015-
Hi pekka
>Or are you asking for instructions on how to fix the alleged Weston
>desktop-shell bug where the black surface is not removed when attaching
>a NULL wl_buffer to the wl_surface?
Actually I ask for instructions on this. Because I use "hide" to switch the
apps. But I met some problems of
On Fri, 20 Nov 2015 10:52:54 +0800
zou lan wrote:
> Hi Pekka
>
> How to not use the black surface behind the fullscreen surface? I want to
Hi Nancy,
are you looking for disabling the black surface in a way that would
work on upstream Weston or be upstreamable, or something you hack just
for yo
Hi Pekka
How to not use the black surface behind the fullscreen surface? I want to
have a try for the special needs to switch the apps. I can't use the
minimize because it can't restore to its original shape.
Thank you.
Best Regards
Nancy
2015-10-13 18:31 GMT+08:00 Pekka Paalanen :
> On Tue, 1
On Tue, 13 Oct 2015 12:19:47 +0200
Joaquim Duran wrote:
> Hello,
>
> Last Friday, we executed Weston for first time. We also view the black
> screen in full screen shell. Weston breaks when desktop shell is used.
Hi Joaquim,
this email thread is about fullscreen windows on desktop shell, not
a
Hello,
Last Friday, we executed Weston for first time. We also view the black
screen in full screen shell. Weston breaks when desktop shell is used.
Joaquim Duran
2015-10-09 9:29 GMT+02:00 Pekka Paalanen :
> On Fri, 9 Oct 2015 10:04:49 +0300
> Giulio Camuffo wrote:
>
>> You get a black surface
On Fri, 9 Oct 2015 10:04:49 +0300
Giulio Camuffo wrote:
> You get a black surface because weston puts a black surface behind the
> fullscreen one even if it has the right size, and it seems like it
> doesn't remove the black surface when the client surface attachs a
> NULL buffer. That's a weston
2015-10-09 9:57 GMT+03:00 zou lan :
> Hi Giulio
>
>>>qtwayland uses wl_shell unless the user explicitly enables xdg_shell,
>>>and right now hide() attachs a NULL buffer. Even in the xdg_shell
>>>case, so that's broken.
>
> Can qtwayland "hide" implement the transparent window in desktop shell
> fu
Hi Giulio
>>qtwayland uses wl_shell unless the user explicitly enables xdg_shell,
>>and right now hide() attachs a NULL buffer. Even in the xdg_shell
>>case, so that's broken.
Can qtwayland "hide" implement the transparent window in desktop shell
fullscreen mode? I know it can work in normal mod
2015-10-08 9:59 GMT+03:00 Pekka Paalanen :
> On Thu, 8 Oct 2015 11:12:42 +0800
> zou lan wrote:
>
>> >>If a client really wants to use the transparency, and does not want
>> opaque black bars, it can be the client's responsibility to produce a
>> buffer that can fill the screen.
>>
>> This is what
On Thu, 8 Oct 2015 11:12:42 +0800
zou lan wrote:
> >>If a client really wants to use the transparency, and does not want
> opaque black bars, it can be the client's responsibility to produce a
> buffer that can fill the screen.
>
> This is what the client wants to. The Qt app call "hide" functio
>>If a client really wants to use the transparency, and does not want
opaque black bars, it can be the client's responsibility to produce a
buffer that can fill the screen.
This is what the client wants to. The Qt app call "hide" function just
wants to implement a function like minimize the window
On Thu, 1 Oct 2015 12:27:21 -0700
Bill Spitzak wrote:
> On Thu, Oct 1, 2015 at 12:50 AM, Pekka Paalanen wrote:
>
> > The black blanket surface behind the window OTOH allows for direct
> > scanout. If black bars are not visible and the client buffer is
> > completely opaque, it is possible to s
On Thu, Oct 1, 2015 at 12:50 AM, Pekka Paalanen wrote:
>
> A fullscreen window with show-through parts is kind of an odd concept,
> IMHO. For maximized I might understand.
>
It seems partially-transparent fullscreen terminals are really popular.
Pad repeat? That requires application awareness t
On Wed, 30 Sep 2015 09:50:09 -0700
Bill Spitzak wrote:
> If you are actually destroying the fullscreen surface, then this sounds
> like a bug.
Yes. It all depends on what "hide" means in Wayland protocol terms with
the applications in question.
> The inability to make a fullscreen surface parti
If you are actually destroying the fullscreen surface, then this sounds
like a bug.
The inability to make a fullscreen surface partially-transparent is on
purpose, though it might be considered a design error. I believe Weston is
trying to pad out the buffer (which may be the wrong shape or size)
Hi all
As I known, when a window is fullscreen, desktop shell will create a black
surface after it. If the window is transparent later, it shows a black
screen. But the app developers maybe except it to be hide.
Just take QWindow function hide for example, app1 start app2, then app2
call hide, it
20 matches
Mail list logo
