Hey,
On Tue, 6 Apr 2010, Thomas Adam wrote:
On Mon, Apr 05, 2010 at 08:10:53PM -0300, Eric Cristianini wrote:
Something i have created myself using some ideas from the said app
(fvwm interface, console interface & exec stuff), it was written
from scratch as i was in need of a very simple app and needed a
number of features that would make almost impossible (not worth) to
modify fvwmbuttons to implement those.
Also it had to be written from scratch 'cause of licensing.
Then I can't say what undefined behaviour you're dragging in...
Mostly the fact that no matter what i do i can't click on anything not
focused (it shows the root menu)
Yup, i applied the NeverFocus to *, but i see that behavior with any
option i use, including the default config that comes with fvwm...
every thing i click on.. the thing shows me the root menu... on top
of the app... very odd/weird.
What? You need to think really hard here. And I mean *really* hard. So
you have this:
Style * NeverFocus
... and yet, clicking on an application in this way brings up the root
window? Utter nonsense. Again, think very carefully.
Nah, i wasn't clear again, the NeverFocus isn't causing the issue nor it
would affect my problem... i just mentioned it 'cause it was removing that
option that i could "see" what was going on... you are absolutely
correct... and the behavior of bringing the root menu (it always bring
the root/builtin menu, not root window) has nothing to do
with this. sorry.
It could be this touchscreen driver you speak of, or some kind of synaptics
issue (if it's using that, etc.) Either way, what you're seeing, has
nothing to do with how FVWM might interpret the events.
Agree, my goal is just to check that fvwm is receiving only what it should
receive, seems not. Doing some tapping on the x11 side for the input
device suggests that it would be receiving more than it should... i just
know what you are going to say...
I tried the same test I have suggested with the "xman", without any
window manager.. it works just ok.. as expected by me... so i would think
that fvwm activates or somehow put in use something that is causing
somepiece of my inputdevice to garble the data fed to x11 or just after
x11 gets it.
That seems to be the cause.. i could not figure out how to get rid of the
extra data nor what causes it to happen when i start fvwm...
Right now i'm trying to find from where (inside of x11 or touch driver)
that extra info is coming and also trying some replay of it.. see if i can
mimic the erratic behavior... or if that data would give me the correct
behavior (from my point of view)
Oh, and consider using 2.5.X, that at *least* has EWMH support. You'd
benefit from that, if nothing else. The fact that you can't deploy that
means your circumstances are the pits. Fix that first, then it might be
worthwhile.
Yes, you are right...the biggest problem is the fact that i can't take
back "quickly" any machines that bombs, the upgrade for the 2.5 was already being considered,
boling down to 2 basic things.. 1- it turning into stable and/or/plus 2- a number of stress tests
for like 2 or 3 weeks nonstop/full time.
Being honest, these new machines (including this one i'm working on) are
to be upgraded in a number of ways..
after installing all the stuff i ran into this problem... once fixed...
i'll work on all linux upgrades and that can include the new version of
fvwm, if i don't run into any issues with it and my code (i guess they
should be mostly compatible.. the module tooling..) works fine i don't see
why not upgrade to 2.5.
Something you guys of fvwm should be proud of is... we have been using
fvwm since.... hummm.... around 1995 (yes, i was there at the start of
linux and wrote a lot of pieces and bolts of its kernel) and we have never
run into a single issue while using fvwm for our purposes... i never had
a single problem with it being used on desktops or weirdo apps. And if i
recall well.... we have fvwm since linus kernel 1.1/1.2
Keep up the good work.
thank you
-- Thomas Adam
Eric
