Tiny Core Extensions > TCE Tips & Tricks

Wine: Getting text by key presses into wine text fields

(1/1)

TinyErestor:
Hi,
in http://forum.tinycorelinux.net/index.php/topic,21892.0.html is written:

--- Quote ---but I cannot enter text.
--- End quote ---
and

--- Quote ---I remember a  post about trouble adding text into wine run progs which I don't think was solved
--- End quote ---
.
So I share my workaround to get text into such fields:
I use xvkbd and put the focus into the text field and use a virtual key to enter the first letter. After that, also physical keys enter letters into the text field.

Regards

Juanito:
I believe text entry works in the 9.x x86 version of wine, no?

labeas:
I'm battling with a similar problem:
 getting text by key presses into other process.

AFAIR it can be done by using: fg, bg, <pid>.

Years ago I managed to select for playing, any 1 of N *.wav,
having only an on/of-power-switch to my battery-operated RPi.
Now I can't even understand [nor find documentation] how multiple
PIDs can give extra <control>.
Where to find ?

labeas:
sometimes you need to put ideas to writing, to open the OLD brain.
AFAIR one pid started the timer and updated nonvolatile mem;
while the other pid played the sound:
  STARTING from where the PREVIOUS session had saved the timer.
This allowed the RPi to play the NEXT, after previous power-down *.wav.
But how did Time map-to the position in N ordered *.wav files.
In one file: yes; but N-files are <scattered>.
OK: play 1; play 2; ….play N *IS* linearly ordered in time.
 Sorry for writing while/in-order-to thinking.

Juanito:

--- Quote from: labeas on August 13, 2019, 06:02:08 AM ---I'm battling with a similar problem:
 getting text by key presses into other process.

--- End quote ---

It is not a similar problem, the wine problem was due to something to do with fontconfig and a setting in the wine config.

Navigation

[0] Message Index