flwm_topside bug?

[thane]

In Tiny Core Linux 64-bit flwm_topside, it appears that if you click on a window, then move the cursor to a different window and click on one of that window's controls, the focus stays on the original window and it's the one that responds to the control click.

Sorry, kind of a long-winded description but can't think of how else to describe it!

Thane

[Leee]

In Tiny Core Linux 64-bit flwm_topside, it appears that if you click on a window, then move the cursor to a different window and click on one of that window's controls, the focus stays on the original window and it's the one that responds to the control click.

Sorry, kind of a long-winded description but can't think of how else to describe it!

Thane

I'm not able to duplicate this on Tiny Core 16.0, x86_84.

I killed off jwm and started flwm_topside (no reboot) then opened to terminal windows from the wbar icon.  Made one of them active then licked the close button on the other one.  The one on which I clicked the close button did close and the other did not.

FWIW, I have been fooling around with MikeLockmoore's fluff_testing extension so maybe it has loaded something relevant.  Equally possible that I just didn't understand the issue completely because... y'know... me.     

---

Edit as of twenty minutes later:

The regular flwm seems to behave the same as flwm_topside - which is good.


As an aside, I just realized that a bunch of my personal tweaks and customizsations (an icon for this, a display for that, things not directly relevant to the window manager itself but sometimes relevant to the overall system) are attached to the jwm "tray"... and they don't appear in the flwm tray at all! (Or should I say they don't appear in the flwm "no tray".)  So there's a whole nother project to play with.

[thane]

Hi Leee, try opening two windows and then switching from one to the other. When I click on the other window and then use a control, it works fine. However if I click on one window and then move the cursor to the other window and click on a control, it's the original window that responds. Note however that I'm using a Lenovo ThinkPad, which may be a factor.

[Leee]

Hi Leee, try opening two windows and then switching from one to the other. When I click on the other window and then use a control, it works fine. However if I click on one window and then move the cursor to the other window and click on a control, it's the original window that responds. Note however that I'm using a Lenovo ThinkPad, which may be a factor.

Y'know, if you just had a Compaq Deskpro instead of that new-fangled Thinkpad...   

I want to reboot for a clean start before I dig any deeper, but I have to go out for a bit so it will be a few hours.

[Rich]

Hi thane
I was able to duplicate the issue.
It appears only the Horizontal Maximize and Vertical Maximize
buttons are affected.

To reproduce:
Open 2 terminals.

Click Horizontal Maximize or Vertical Maximize on the terminal
that does not have focus. The terminal with focus responds.

The Close, Minimize, and Window shade buttons work correctly.

[Rich]

Hi thane

... then move the cursor to a different window and click on one of that window's controls, the focus stays on the original window ...

That part of the behavior has not changed. I just checked under TC10 x86 and
TC14 x86_64 and clicking on a Maximize button does not grab focus.

[thane]

Thanks Rich, I don't recall encountering this in earlier versions of TC but of course that doesn't mean it wasn't there. Lately I've been listening to podcasts while playing Spider, so I spend a lot of time with two windows open side by side and just happened to run into this.

[Rich]

Hi thane

Thanks Rich, I don't recall encountering this in earlier versions of TC ...

Earlier versions do not have the Maximize buttons controlling the wrong window.

It's just that clicking on window frame controls does not grab focus, and I don't think it
ever has.