Hmm... could it be that the program refuses to accept window manager
assigned size and continually sends new requests? Bad, bad, bad.
It is written using vanilla Swing I belive. Swing normal behaviour is to behave bad bad bad in X. I have tons of application that even find it hard to live in fvwm. One problem is also that it keeps aligning to the wrong coordinates. It's like it can't understand that it has a border around it. If I close the application it remebers it's last state (x,y, h, w). However, when starting it again it get's the wrong idea about where it should be. It forgets that 0,0 should be relative to the "frame/window/border" it lives in. So using a pwn workspace constantly gives me the window border outside the actual workspace. Is there perhaps a flag in kludges that can force it in the right place. This is not a problem if I run the application inside a ion-frame (but then I have the other problem I mentioned).
It's a little bit like the acrobat fix. If you can't change the induhvidual, well then you have to change the world <ehh>
once I add support for window stacking management, it should be trivial to add a "keep on top" floatws layer and just set the target for these dialogs to this workspace.
That sounds very good. I can surly live with the full-screen solution until then. ie, not critical, just a major.
So just change the Ion key bindings?
Hee, well I had too. Unfortunently I'm also running this in windows X server (XWin32) and it doesn't like you to use F1 and the Alt+Tab key (windows take precedence there). So I adjusted all commands for navigation to use arrow-keys instead (Mod1+Left, Mod1+Control+Left, Mod1+Control+Shift+Left -> /ws/frame/tab). It was my old setting for moving the mouse in fvwm (/ws/big-move/small-move) so that works.
But the functional keys that ion uses works for me (well, not works, but it would). I like them. Unfortunently using F1-F12 with or without Mod1 or other combinations is rather booked by a lot of applications. So I could imagine that I would press <esc><esc> (hehe vi-user) and then have it toggle to "ion-key-control" .. and then use whatever keys assigned to ion, default keys. Control+K and lots of these combinations are allready used by my editor too.. and I figured that it would be a shame that *one* application (bad bad bad application also) would control what keys I have to assign for the window-manager. Also, it would only work until I get another application that has it's keys (like vi/emacs/etc). It's a temporary solution.
So .. yes, I can re-assign, but I would rather be able to assign a hot-hot key combination that would toggle between application scope and ion-scope whenever nesseccary. And the default way in ion of knowing when and how that would be, is via kludges I guess.
Cheers, /Niclas -- Niclas Olofsson - http://www.ismobile.com Product Development, isMobile, Aurorum 2, S-977 75 Lule�, Sweden Phone: +46(0)920-75550 Mobile: +46(0)70-3726404
