I've got a strange issue with wmctrl : I'm trying to bring on top a virtual keyboard with by clicking on a button in another application (GUI app), but it seems not to work.
The other application (the GUI) is in Python created with the tkinter module.
It's strange because when the GUI is not in fullscreen mode it works fine, the Keyboard is bringing on top of the GUI. But when the GUI is set in fullscreen mode nothing appends, and I didn't get any error.
So if you have an idea I'm listening :)
thkx
Related
The python script takes some time to run so I want a console window to appear and somehow print messages to it while the program is running. At the moment I have a tkinter that pops up and when I hit "Run" - I do not know if it's working or if it is hanging. How do I force a console window?
Thank you.
I have a Kivy app under development. When testing it on my touchscreen laptop (Ubuntu 20.04), I noticed a couple things.
Using the mouse, there are red dots appearing after right-clicks, which simulate multitouch points.
When touching buttons using the laptop touchscreen, there is a 300ms-ish delay before those buttons show the pressed state and register the press event. Similar to what happened initially with mobile web browsers. It makes the app feel sluggish and not practical for my use case.
I also tried running it on a Raspberry Pi using the official 7' touchscreen. There is no touch delay at all, the UI feels snappy. How can I get the same result on my computer?
Documentation says that the input driver is responsible for those differences.
So far, I attempted the following:
Disabling multitouch from the config (mouse = mouse,disable_multitouch); the right-click simulation disappears but the delay is still there
Removing mouse from the config as I would have suspected a conflict: mouse inputs are no longer registered and touch still does not work.
Adding touch drivers in the config gave no improvements:
mtdev_%(name)s = probesysfs,provider=mtdev
hid_%(name)s = probesysfs,provider=hidinput
The startup log shows some warnings:
[WARNING] [MTD ] Unable to open device "/dev/input/event7". Please ensure you have the appropriate permissions.
[WARNING] [MTD ] Unable to open device "/dev/input/event13". Please ensure you have the appropriate permissions.
Looks like a permissions issue. How can I fix it?
I actually found the culprit - it was Ubuntu 20.04 itself.
The delay did not appear in Ubuntu 22.04 after an upgrade.
Explanation:
The OS input system was delaying the delivery of touch start events to all of the applications.
To see if there is such a delay, it is possible to use xinput test-xi2 and interact with the little window using a touchscreen. The console output shows the events as they are received by the window.
I am working on a small project using python and pysimplegui . Here my application needs to have a option "Run at start up" which when checked would automatically run my application during windows starts up. Also I would like to know how can I put my application to the system tray. Like if I click on the minimize button , it'll go to the system tray.
Thank you!
To Run On Startup
Create shortcut of your application & copy it.
Press win + R
Run Command: shell:startup, Hit ok
3.And paste the shortcut in this folder
To Add In System Try
Go to the SETTINGS window and choose System.
[In the SYSTEM window, select Notifications & actions. Here you can select the option that reads “Select which icons appear on the taskbar”4
In the SELECT WHICH ICONS APPEAR ON THE TASKBAR window, you can turn on or off the icons in whichever way you prefer.
I tried the solution provided in Tkinter GUI does not run properly when auto boot Tkinter, however GUI does not run properly when auto boot and got my python script with tkinter to run correctly and automatically after reboot.
The GUI interface kind of disappear. I get a black background, shows "Open Box" application when I tried to close, instead of the normal menu and wall paper. I can still right click and open web browser and a terminal. I tried running "startx" from terminal after some googling but received an error message.
How do I get the raspbian GUI interface working with the solution provided in link above? Any help is very much appreciated.
#!/usr/bin/python
chmod +x /home/pi/Desktop/test.py
nano /home/pi/.config/lxsession/LXDE-pi/autostart
#/home/pi/Desktop/test.py
I'm not sure it's possible to do this, but is there any way for Tkinter to know which monitor you are currently using (in a multiple-monitor setup)?
I might be running with my laptop and external monitor, and run a script from either screen. Ideally, the Tkinter window generated by that script would open on the screen I'm currently working on.
I know how to set the geometry to force the window to open on the main monitor or on a secondary monitor, but I'm wondering if there's a way to figure out which is currently being used.
Thanks!