Tommaso Cucinotta wrote:
> possibilities. Just need to fix what else is needed in order to have the 
> test run properly on a non-Italian machine (I have to find an English 
> installation somewhere and try).

you dont know what box are you opening :) there are many strange issues
which affect whether lang switching works on different setups.

the test would now suppose that you run english version of UI, but i see it as
less complicated thing to demand, than that lang switching works...

>> i also think it would be much more robust to use lfuns like buffer-save
>> than alt+f + s and so on...
> That is still possible, but it achieves a different goal: if you dispatch 
> the LFUN, you test the LFUN in itself. If you emulate the user behavior, 
> then you test the LFUN combined with the GUI code. For example, 
> qt4/FindAndReplace.cpp contains code for cycling through documents, that 
> dispatches multiple LFUNs for searching across them, in reaction to a 
> single user interaction (Find Next). These are 2 different types of test 
> and both of them make sense, AFAICS. Still, in the current scripts you can 
> base everything on \Axwhatever, if you wish. Unfortunately, in the supplied 
> args to the FINDADV LFUN, there are the search and replace buffers :-(, 
> which are entire LyX documents. 

my proposal was not about using lfuns for everythhing but using it for things
you which are not tested. if you test advanced search then there is no point to
make the test crash because 3D menu effects of some WM collide with delay time
needed for next char or similar. issuing buffer-new/load etc makes the same
without entering menu. of course for movement inside findadv there is no other
way. 

>It would be far more burdening to provide 
> those .lyx contents in the script, rather than typing the few key presses 
> that create them from scratch using the GUI :-).

no problem with that.

> I don't know whether you share at least partially the above.

i wouldn't care about those matters if it worked. but it did not, so i was
merely suggesting how to make this work flawlessly for others. if most of the
tests works only on your setup it will be only you who will use this -- i'm
fine with that as well, just not gonna touch it again ;)

pavel

Reply via email to