Hi, and thank you so much for this invaluable tool. Florence is the best gnome keyboard I've tried so far. I am using it on my pc it works fine.
But when i use it on i.mx6 which is connected to lcd touch screen with os Linux LZ50 4.9.88-10183-ge88eca2 #12 SMP PREEMPT Sat Apr 17 01:16:19 CDT 2021 armv7l GNU/Linux os. i am using debian revision 9.13. Debian GNU/Linux 9 (stretch).
i am writing below command on command line:
florence -f -d -u florence.conf
i am facing some issue :
(florence:3431): Gdk-ERROR **: The program 'florence' received an X Window System error.
This probably reflects a bug in the program.
when i am skip this error using -d command at that time
when i am pressing the key on my lcd screen of i.mx6. i am not receiving any character output.
why this is happening ?
i am getting below log:
CONF:scalex=<16.5>
CONF:scaley=<16.5>
CONF:always-on-top=<true>
CONF:task-bar=<false>
CONF:resizable=<false>
CONF:decorated=<false>
CONF:xpos=<0>
CONF:ypos=<570>
Your screen does not support alpha channel. Semi-transparency is disabled
CONF:transparent=<true>
CONF:keep-on-top=<true>
CONF:trayicon=<true>
CONF:startup-notification=<true>
CONF:timer=<0.0>
DBus name aquired: org.florence.Keyboard
CONF:system-font=<true>
CONF:mouseover=<'#0000FF'>
Using configuration file florence.conf
CONF:hide-on-start=<false>
CONF:auto-hide=<false>
Executing method show
CONF:auto-hide=<false>
CONF:floaticon=<true>
Your screen does not support alpha channel. Semi-transparency is disabled
CONF:icon-xpos=<0>
CONF:icon-ypos=<0>
Key 0x16e55a0 (type 0): Event 0 received : Switching from state 1 to 1 (fsm 0)
sending press event
CONF:sounds=<false>
Key 0x16e55a0 (type 0): Event 2 received : Switching from state 1 to 0 (fsm 0)
Key 0x16e55a0 (type 0): Event 0 received : Switching from state 0 to 0 (fsm 0)
keyboard layout found: <english (us)="">
keyboard layout symbol name=<pc+us+inet(evdev)>
new xkb symbol found: <us>
XKB state notify event received
CONF:activated=<'#FF0000'>
Key 0x16e55a0 (type 0): Event 1 received : Switching from state 0 to 0 (fsm 0)
sending release event
Key 0x16e55a0 (type 0): Event 3 received : Switching from state 0 to 1 (fsm 0)
CONF:ramble-button=<true>
Key 0x16e56c8 (type 0): Event 0 received : Switching from state 1 to 1 (fsm 0)
sending press event
Key 0x16e56c8 (type 0): Event 2 received : Switching from state 1 to 0 (fsm 0)
Key 0x16e56c8 (type 0): Event 0 received : Switching from state 0 to 0 (fsm 0)
Key 0x16e56c8 (type 0): Event 1 received : Switching from state 0 to 0 (fsm 0)
sending release event
Key 0x16e56c8 (type 0): Event 3 received : Switching from state 0 to 1 (fsm 0)
Key 0x16b8138 (type 0): Event 0 received : Switching from state 1 to 1 (fsm 0)
sending press event
Key 0x16b8138 (type 0): Event 2 received : Switching from state 1 to 0 (fsm 0)
Key 0x16b8138 (type 0): Event 0 received : Switching from state 0 to 0 (fsm 0)
Key 0x16b8138 (type 0): Event 1 received : Switching from state 0 to 0 (fsm 0)
sending release event
Key 0x16b8138 (type 0): Event 3 received : Switching from state 0 to 1 (fsm 0)
Key 0x16e27a0 (type 0): Event 0 received : Switching from state 1 to 1 (fsm 0)
sending press event
Key 0x16e27a0 (type 0): Event 2 received : Switching from state 1 to 0 (fsm 0)
Key 0x16e27a0 (type 0): Event 0 received : Switching from state 0 to 0 (fsm 0)
Key 0x16e27a0 (type 0): Event 1 received : Switching from state 0 to 0 (fsm 0)
sending release event
Key 0x16e27a0 (type 0): Event 3 received : Switching from state 0 to 1 (fsm 0)
Key 0x16e55a0 (type 0): Event 0 received : Switching from state 1 to 1 (fsm 0)
sending press event
Key 0x16e55a0 (type 0): Event 2 received : Switching from state 1 to 0 (fsm 0)
Key 0x16e55a0 (type 0): Event 0 received : Switching from state 0 to 0 (fsm 0)
Key 0x16e55a0 (type 0): Event 1 received : Switching from state 0 to 0 (fsm 0)
sending release event
Key 0x16e55a0 (type 0): Event 3 received : Switching from state 0 to 1 (fsm 0)
Key 0x16e5410 (type 0): Event 0 received : Switching from state 1 to 1 (fsm 0)
sending press event
Key 0x16e5410 (type 0): Event 2 received : Switching from state 1 to 0 (fsm 0)
Key 0x16e5410 (type 0): Event 0 received : Switching from state 0 to 0 (fsm 0)
Key 0x16e5410 (type 0): Event 1 received : Switching from state 0 to 0 (fsm 0)
sending release event
Key 0x16e5410 (type 0): Event 3 received : Switching from state 0 to 1 (fsm 0)
Key 0x16e5410 (type 0): Event 0 received : Switching from state 1 to 1 (fsm 0)
sending press event
Key 0x16e5410 (type 0): Event 2 received : Switching from state 1 to 0 (fsm 0)
Key 0x16e5410 (type 0): Event 0 received : Switching from state 0 to 0 (fsm 0)
Key 0x16e5410 (type 0): Event 1 received : Switching from state 0 to 0 (fsm 0)
sending release event
Key 0x16e5410 (type 0): Event 3 received : Switching from state 0 to 1 (fsm 0)</true></us></pc+us+inet(evdev)></english></false></true></false></false></false></true></true></true></true></true></false></false></false></true>
Here sending release event happening but output of released key not coming.
Could someone please help me to fix that?
i have installed at-spi then it remove below error
(florence:3431): Gdk-ERROR **: The program 'florence' received an X Window System error.
This probably reflects a bug in the program.
But still sending release event happening on click of key but output of released key not coming.
i have used your qt demo code for qt 5. i have started /usr/lib/at-spi2-core/at-spi2-registryd & before run my program but i am unable to receive clicked character on line edit.
why this is not receiving clicked character ?
i have seen that there is response is coming unpredictably and at random time . so if possible tell me why this is happening?
some times killing the florence keyboard process still below things make it open instead close this process
usr/lib/at-spi2-core/at-spi-bus-launcher
/usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
/usr/lib/at-spi2-core/at-spi2-registryd --use-gnome-session