Scott wrote:
As far as I can tell, it works correctly with the patch applied. :)
Scott had reported: "Dillo sometimes raises its window when clicked, instead of letting the window manager do its job. Usually if I have a window partially hidden, I don't want it raised... Apps should not try to do their own window management." fltk's Window::handle() has: #if USE_X11 case PUSH: // Unused clicks should raise the window. Windows unfortunatly // raises the window on *all* clicks so we don't bother except on X. if (shown()) XMapRaised(xdisplay, i->xid); #endif Aforementioned patch attached.
On Sun, Aug 02, 2009 at 05:14:47PM +0000, corvid wrote:
Scott wrote:
As far as I can tell, it works correctly with the patch applied. :)
Scott had reported: "Dillo sometimes raises its window when clicked, instead of letting the window manager do its job. Usually if I have a window partially hidden, I don't want it raised... Apps should not try to do their own window management."
Sorry, I don't get the idea of the bug. IIUC the problem is that a partially hidden Dillo window raises upon clicking it. I hesitate because Firefox and even terminals here behave that way. Please explain. -- Cheers Jorge.-
Jorge wrote:
On Sun, Aug 02, 2009 at 05:14:47PM +0000, corvid wrote:
Scott wrote:
As far as I can tell, it works correctly with the patch applied. :)
Scott had reported: "Dillo sometimes raises its window when clicked, instead of letting the window manager do its job. Usually if I have a window partially hidden, I don't want it raised... Apps should not try to do their own window management."
Sorry, I don't get the idea of the bug. IIUC the problem is that a partially hidden Dillo window raises upon clicking it. I hesitate because Firefox and even terminals here behave that way. Please explain.
Other windows don't for me. Dillo does if it's a new window/new tab or if I'm clicking below the bottom of the text when the page is very short. I imagine your WM must be set to do it...
On Sun, Aug 02, 2009 at 07:27:54PM +0000, corvid wrote:
Jorge wrote:
On Sun, Aug 02, 2009 at 05:14:47PM +0000, corvid wrote:
Scott wrote:
As far as I can tell, it works correctly with the patch applied. :)
Scott had reported: "Dillo sometimes raises its window when clicked, instead of letting the window manager do its job. Usually if I have a window partially hidden, I don't want it raised... Apps should not try to do their own window management."
Sorry, I don't get the idea of the bug. IIUC the problem is that a partially hidden Dillo window raises upon clicking it. I hesitate because Firefox and even terminals here behave that way. Please explain.
Other windows don't for me. Dillo does if it's a new window/new tab or if I'm clicking below the bottom of the text when the page is very short. I imagine your WM must be set to do it...
Oh, now I see it (with TWM). Please commit. -- Cheers Jorge.-
On Mon, Aug 03, 2009 at 12:17:35PM -0400, Jorge Arellano Cid wrote:
On Sun, Aug 02, 2009 at 07:27:54PM +0000, corvid wrote:
Jorge wrote:
On Sun, Aug 02, 2009 at 05:14:47PM +0000, corvid wrote:
Scott wrote:
As far as I can tell, it works correctly with the patch applied. :)
Scott had reported: "Dillo sometimes raises its window when clicked, instead of letting the window manager do its job. Usually if I have a window partially hidden, I don't want it raised... Apps should not try to do their own window management."
Sorry, I don't get the idea of the bug. IIUC the problem is that a partially hidden Dillo window raises upon clicking it. I hesitate because Firefox and even terminals here behave that way. Please explain.
Other windows don't for me. Dillo does if it's a new window/new tab or if I'm clicking below the bottom of the text when the page is very short. I imagine your WM must be set to do it...
Oh, now I see it (with TWM). Please commit.
Yes, but we should mark it as a workaround for an FLTK issue and report it to FLTK.
On Mon, Aug 03, 2009 at 06:20:50PM +0200, Johannes Hofmann wrote:
On Mon, Aug 03, 2009 at 12:17:35PM -0400, Jorge Arellano Cid wrote:
On Sun, Aug 02, 2009 at 07:27:54PM +0000, corvid wrote:
Jorge wrote:
On Sun, Aug 02, 2009 at 05:14:47PM +0000, corvid wrote:
Scott wrote:
As far as I can tell, it works correctly with the patch applied. :)
Scott had reported: "Dillo sometimes raises its window when clicked, instead of letting the window manager do its job. Usually if I have a window partially hidden, I don't want it raised... Apps should not try to do their own window management."
Sorry, I don't get the idea of the bug. IIUC the problem is that a partially hidden Dillo window raises upon clicking it. I hesitate because Firefox and even terminals here behave that way. Please explain.
Other windows don't for me. Dillo does if it's a new window/new tab or if I'm clicking below the bottom of the text when the page is very short. I imagine your WM must be set to do it...
Oh, now I see it (with TWM). Please commit.
Yes, but we should mark it as a workaround for an FLTK issue and report it to FLTK.
Exactly! (even though I have more hope for their 1.3 branch). -- Cheers Jorge.-
Jorge wrote:
On Mon, Aug 03, 2009 at 06:20:50PM +0200, Johannes Hofmann wrote:
On Mon, Aug 03, 2009 at 12:17:35PM -0400, Jorge Arellano Cid wrote:
On Sun, Aug 02, 2009 at 07:27:54PM +0000, corvid wrote:
Jorge wrote:
On Sun, Aug 02, 2009 at 05:14:47PM +0000, corvid wrote:
Scott wrote: > As far as I can tell, it works correctly with the patch applied. :)
Scott had reported: "Dillo sometimes raises its window when clicked, instead of letting the window manager do its job. Usually if I have a window partially hidden, I don't want it raised... Apps should not try to do their own window management."
Sorry, I don't get the idea of the bug. IIUC the problem is that a partially hidden Dillo window raises upon clicking it. I hesitate because Firefox and even terminals here behave that way. Please explain.
Other windows don't for me. Dillo does if it's a new window/new tab or if I'm clicking below the bottom of the text when the page is very short. I imagine your WM must be set to do it...
Oh, now I see it (with TWM). Please commit.
Yes, but we should mark it as a workaround for an FLTK issue and report it to FLTK.
Exactly!
(even though I have more hope for their 1.3 branch).
Judging from the comment I mentioned:
fltk's Window::handle() has: #if USE_X11 case PUSH: // Unused clicks should raise the window. Windows unfortunatly // raises the window on *all* clicks so we don't bother except on X. if (shown()) XMapRaised(xdisplay, i->xid); #endif
they seem to view it as correct, although it seems strangely arbitrary to me.
participants (3)
-
corvid＠lavabit.com -
jcid＠dillo.org -
Johannes.Hofmann＠gmx.de