* Tuomo Valkonen <[EMAIL PROTECTED]> [04/05/22 22:20]: > > --cut: floatws.lua, floatframe_bindings > > mclick(DEFAULT_MOD.."Button1", WRegion.raise), > > --end cut > > > > When I removed 'DEFAULT_MOD..' part, switching just stopped to work. > > What am I doing wrong? > Plain buttons are not grabbed so that the application has a chance to > receive them.
Does it mean that I can't setup ION so that just a mouse button click will raise window under mouse cursor? Why doesn't this binding (ALT + Button1) work for windows in IonWS? How does other WMs handle single clicks and not conflict with applications? I'm sorry if I'm asking silly questions or wrongly expect from ION to behave in the way some other WMs behave. I'm a software developer, and I'm coming from IceWM. Main advantage of ION compared to IceWM to me is that it's very easy in ION to organize terminal windows and switch between them - I have full control on window placement with using IonWS inside FloatWS, and can quickly switch between windows inside tabs. I don't use IonWS as a primary WS because of relatively small screen and low resolution - it's 15 inch Sony flat screen in 1024x768 resolution. With my vision I can have maximum one full-size 80x37 xterm per workspace, and I need to have a lot of xterms - mutt, irssi, a few vi windows, a window to run MySQL server and another one for the client. I wonder what's the best ION setup in my case. PS If experienced ION users could share their ION config files with me, it will be highly appreciated. I still haven't figured out how to switch from keyboard between two IonWSs created as windows inside FloatWS. -kostja
