Hi, * [email protected] <[email protected]> [2009-10-09 14:03]: > >What is matchbox keyboard? Do you have this with other applications as well? > > matchbox-keyboard is an app that displays a keyboard and produces the > respective 'keystroke' for other applications when you click on a key. > > think of a phone/pda with a touchscreen display but no keyboard => > matchbox-keyboard can be used with a stylus for keyboard input.
Ok > i tried the same with xclock (changing the application name in the rc.xml > from > "" to "xclock") with the following result: > - the maximized (x and y) window still uses the whole screen except for the > panel, especially it's still partly covered by xclock. that's different in > that > it does not use just the lower half of the screen. > - there's still the gap at the bottom. I just installed matchbox-keyboard. How did you maximize it anyway? It doesn't have any focus. And resizing it by hand results in some funny effects. I still don't get your problem, can you please try to rephrase what happens and what would you expect to happen? "if a window is 'maximized', it won't draw over the panel, but if matchbox-keyboard is started, the window gets resized" Which window is meant here by "the window"? maximize = maximize until you hit any panels and do not steal focus fullscreen = completely maximize over panels and steal focus > >If the application is messed-up (in this case matchbox keyboard) openbox can > >hardly do anything against that. > > i tried matchbox-keyboard with a few wms. this behaviour at least occured > only > with openbox. > what makes it especially strange for me is that the existence of one window > (matchbox-keyboard) makes the other (xy maximized) window use just the lower > half of the screen. i don't want to claim that this can not actually be > caused > by some error in matchbox-keyboard, it just seems very counterintuitive to me > (plus this happens only with openbox). Please tell me exactly the steps to reproduce, key strokes and stuff, I have no idea what you're talking about. > i also don't want to claim that the problem can't be a lack of understanding > of > the configuration by me. but then the correct configuration (or the error in > the config) is at least not obvious (to me, or to an average user so to speak > :) > > maybe it helps to explain what i'm trying to achieve: > - a panel at the top of the screen. I have that > - the matchbox-keyboard app is started and stopped as needed. if it is > running, > it should be displayed at the bottom of the screen. That's not to the windowmanager to decide, at least not alone. > - any other windows are to use the space between the panel and the > matchbox-keyboard (if it is running) or the whole space except for the panel > (if matchbox-keyboard is not running). So matchbox has to behave like a panel which it obviously is not doing. I gave the X properties of that to upstream asking if it's an application bug. I expect it to be but to be honest I don't know. Cheers Nico -- Nico Golde - http://www.ngolde.de - [email protected] - GPG: 0xA0A0AAAA For security reasons, all text in this mail is double-rot13 encrypted.
pgpg95yc01WDL.pgp
Description: PGP signature
