Hi there,
Follows...
On Mon, 5 Apr 2010, Thomas Adam wrote:
On Mon, Apr 05, 2010 at 06:48:22PM -0300, Eric Cristianini wrote:
Hi guys,
I have developed a module for/with fvwm 2.4.20 and have it deployed
over 1.000 machines, all touchscreen, no keyboard/mouse. Basically
its like the FvwmButtons application.. but it let me create and
group buttons.. or have them floating.
So this is bespoke? Is *it* FvwmButtons, or something you've created
yourself? If so, I dread to think what it might be, but hopefully it's
academic for the purposes of this email.
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.
So far, the behavior with the "NeverFocus" style option was... "any
button i click gets activated".. and thats the correct behavior i
want.. any button on the screen that gets clicked.. do its action.
Err, no. NeverFocus simply doesn't pass the click to the application at
all to focus it. As such, you can still use the click to do thing with the
application, but if it's a terminal, for instance, typing intp it is going
to be a problem.
True, i only mentioned the NeverFocus to let you guys know that i don't
really care about focus, just need it to respond the click stimulus. No
data is being input. Should have been clearer.
Now, with {Mouse,Sloppy}Focus, the *EFFECT* (and I mean that strongly) will
be such that the pointer entering into said application which has NeverFocus
applied will look as though the clicks are to the window with focus -- but
only because of how NeverFocus works. Please tell me you can understand
this?
Yup, no problems. Thats how it should be (and how i want it).. my use is
as it prevents the window to "visually receive focus", as on some pices of
my app that would allow the user to notice focus/no focus.. something i
don't want to.
Yesterday i had to do a clean install in an identical machine, but
this time i installed from scratch.. fvwm 2.4.20 same linux as the
other machines....
Use 2.5.X -- if you can't roll that out, more fool you.
That would implicate on deploying an upgrade package on 1.000+ machines
that i have no way to take back if something goes wrong... I was already
considering the 2.5 version, but on the next bigger release.. we are going
to deploy 500+ new machines with a new version of this app... There are no
plans to upgrade the older ones in field... but to upgrade then with the
new system by steps, after the new system is running and testes.
I understand what you mean, and i agree.. besides not marked as stable the
2.5 has a number of benefits.
For my surprise the click/focus behavior is way diff now...
everytime i click something not focused it just do nothing....
removing my mouse bindinds and using the original fvwm config.... i
can see it shows me the root (builtin) menu... even if i clicked on
an app (not focused)
Sounds like a Numlock problem to me, but can't say for certain.
No keyboard and no mouse on the machines.... only touchscreen.
To make things a bit easier to understand... lets say i open 2
"xman" for example... side to side... if i click on "help" of the
first.. it will just focus it... if i click on "help" of the
second.. it will move the focus to that... not running the option.
Is this still with NeverFocus? I've noticed some applications ignore this,
most likely because of XSetInputFocus(). What's that? ICCCM you say?
Pfft, like authors listen to that these days...
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.
That said i tried all documented focus/click options, no love... the
point here is the fvwm versions are the same... configuration
ditto... i tried the default fvwm2rc that comes, same thing... but
all the other machines runs fine, with just the install of app and
replacement of system.fvwm2rc
Then are you really running the versions of software you claim?
Yup, slackware linux, linus kernel 2.6.29, fvwm 2.4.20 (binary package
and source code) and latest x11
(from xorg), all machines are identical, UMPC's with openchrome video and touchscreen (usb
interface, egalax)..
-- Thomas Adam
All that said... i'm doing some debugs now, seeing if the touchscreen
driver could be the culprid.. somehow it could send more data than what is
actually happening... 'cause if a plug a regular mouse.. things gets
better... but still not fixed.
Thank you for your time and att, also i would like to apologize about the
today's chat, i didn't good.. usually i don't act like that and i'm sorry.
Best regards from Brazil,
Eric
