Re: keytest.py

Am Montag, 8. Mai 2017 um 09:29:06, schrieb Tommaso Cucinotta > On 07/05/2017 19:46, Kornel Benko wrote: > > Do they fail if retested separately too? > > I tested again just a couple of these, one was keeping failing, another one > succeeded, but I had no time for a proper

Re: keytest.py

ch wmctrl)" == "" ]; then echo "You need to install wmctrl first, try:" @@ -29,7 +29,7 @@ fi PROGRAM_SUFFIX=$(grep -e '#define PACKAGE ' ../../config.h | sed -e 's/#define PACKAGE "lyx\(.*\)"/\1/') -export XVKBD_EXE=../$XVKBD_EXE +export XVKBD_EXE=xvkbd export KEYTEST=../keytest.py LYX_HOME=out-home export LYX_USERDIR=$(pwd)/$LYX_HOME/.lyx$PROGRAM_SUFFIX

Re: keytest.py

findadv-re-05-in.txt: Ok > findadv-re-06-in.txt: FAILED > tabular-footnote-in.txt: Ok > > There were 10 FAILED tests > > T. Latitude E6400 should be fast enough (2.27GHz). Maybe setting def_delay at line keytest.py:374 to some higher value helps? Do they fail if retested separately too? Which QT version? Kornel signature.asc Description: This is a digitally signed message part.

Re: keytest.py

On 07/05/2017 14:35, Kornel Benko wrote: Am Sonntag, 7. Mai 2017 um 02:46:31, schrieb Tommaso Cucinotta On 06/05/2017 14:15, Kornel Benko wrote: Hi Tommaso, could you please test this version? sure, as soon as I get back to a successful compile of LyX on Ubuntu 17.04 :(!

Re: keytest.py

ned errors are back. Inserting the parameter again, tests pass. Tested back and forth, this behaviour was reliable. Also the using of (now not needed) parameter '-wait_idle' for xvkbd_hacked can be removed. Korneldiff --git a/development/autotests/keytest.py b/development/autotests/keytest.py index

Re: keytest.py

Am Dienstag, 25. April 2017 um 09:33:24, schrieb Kornel Benko ... > -xvpar.extend(["-window", lyx_window_name, "-delay", actual_delay, > "-text", keystr]) > +#xvpar.extend(["-window", lyx_window_name, "-delay", actual_delay, > "-text", keystr]) > +

Re: keytest.py

hat removes that ? > > The window name forces keys to be sent to the main LyX window, so whenever > there's a dialog, keytest.py fails to send the key to the dialog, so it's > impossible to dismiss it or anything. Leaving out that parameter, it seems > now keys reach the right win

Re: keytest.py

Hi, On 23/04/2017 16:29, Kornel Benko wrote: \Cq\[Escape] can't remember why I had the window name explicit in keytest. Do you mind trying out the attached one, that removes that ? The window name forces keys to be sent to the main LyX window, so whenever there's a dialog, keytest.py fails

Re: keytest.py

Am Sonntag, 23. April 2017 um 16:20:48, schrieb Tommaso Cucinotta > On 23/04/2017 10:34, Kornel Benko wrote: > > Prefixing \[Escape] with \Ax does the trick :), e.g. "\Ax\[Escape]\Cq" > > (without \Cs) > > Sometimes we need to not save the buffer. > > what was the \Ax for,

Re: keytest.py

On 23/04/2017 10:34, Kornel Benko wrote: Prefixing \[Escape] with \Ax does the trick :), e.g. "\Ax\[Escape]\Cq" (without \Cs) Sometimes we need to not save the buffer. what was the \Ax for, then ? And, if it's for dismissing the (save?) dialog, then shouldn't it be like: \Cq\[Escape] ?

keytest.py

eturn] KK: \Axbuffer-export luatex\[Return] KK: \[Tab]\[Return] +KK: \Axbuffer-write\[Return] +KK: \[Tab]\[Return] TestEnd Lang C Assert ! pcregrep -M "support/FileName.cpp .* creating path '/.*/lib/images'" lyx-log.txt diff --git a/development/autotests/keytest.py b/development/autote

[PATCH] keytest.py: do not print the same thing twice

keytest.py now only prints one time the command that it is executing for an assert. The command is already printed in the function responsible for executing it, so it is not necessary to print the command before calling that function. --- development/autotests/keytest.py |1 - 1 file changed

Re: [PATCH] keytest.py: do not print the same thing twice

Am Montag, 4. Februar 2013 um 03:07:13, schrieb Scott Kostyshak skost...@lyx.org keytest.py now only prints one time the command that it is executing for an assert. The command is already printed in the function responsible for executing it, so it is not necessary to print the command before

Re: [PATCH] keytest.py: do not print the same thing twice

On Mon, Feb 4, 2013 at 3:11 AM, Kornel Benko kor...@lyx.org wrote: Am Montag, 4. Februar 2013 um 03:07:13, schrieb Scott Kostyshak skost...@lyx.org keytest.py now only prints one time the command that it is executing for an assert. The command is already printed in the function responsible

[PATCH] keytest.py: do not print the same thing twice

keytest.py now only prints one time the command that it is executing for an assert. The command is already printed in the function responsible for executing it, so it is not necessary to print the command before calling that function. --- development/autotests/keytest.py |1 - 1 file changed

Re: [PATCH] keytest.py: do not print the same thing twice

Am Montag, 4. Februar 2013 um 03:07:13, schrieb Scott Kostyshak <skost...@lyx.org> > keytest.py now only prints one time the command that it is executing for > an assert. The command is already printed in the function responsible > for executing it, so it is not necessary to pr

Re: [PATCH] keytest.py: do not print the same thing twice

On Mon, Feb 4, 2013 at 3:11 AM, Kornel Benko <kor...@lyx.org> wrote: > Am Montag, 4. Februar 2013 um 03:07:13, schrieb Scott Kostyshak > <skost...@lyx.org> > >> keytest.py now only prints one time the command that it is executing for > >> an assert. The comman

Re: keytest.py, undocumented controls

On Sat, Jan 12, 2013 at 4:35 AM, Kornel Benko kor...@lyx.org wrote: Hi Tommaso, I wanted to check the description of controls in hello-world-in.txt with the script keytest.py. So far, there exist some non-described controls Sleep Loop RaiseLyx . OK, 'Sleep' was easy. But what

Re: keytest.py, undocumented controls

On Sat, Jan 12, 2013 at 4:35 AM, Kornel Benko <kor...@lyx.org> wrote: > Hi Tommaso, > > I wanted to check the description of controls in hello-world-in.txt with the > script keytest.py. > > So far, there exist some non-described controls > > Sleep > > Lo

keytest.py, undocumented controls

Hi Tommaso, I wanted to check the description of controls in hello-world-in.txt with the script keytest.py. So far, there exist some non-described controls Sleep Loop RaiseLyx . OK, 'Sleep' was easy. But what should 'Loop' do? At least in keytest.py there you can find

keytest.py, undocumented controls

Hi Tommaso, I wanted to check the description of controls in hello-world-in.txt with the script keytest.py. So far, there exist some non-described controls Sleep Loop RaiseLyx . OK, 'Sleep' was easy. But what should 'Loop' do? At least in keytest.py there you can find