ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

DonationCoder.com Software > Find And Run Robot

v1.13.01 test

<< < (2/3) > >>

mouser:
alexp, can you elaborate a little.
is the # corresponding to the last # you typed when you previously launched a program?
do you have an unusual keyboard? what setting do you have configured for it to show in the search window on launch.

alexp:
Yeah, it seems to be the # of the last program launched.

Don't have a strange keyboard (Logitech® Cordless Desktop® S 510)

Here's sceenshots of my options:

v1.13.01 test

v1.13.01 test

v1.13.01 test

Jan-S:
Hi!

I've just upgraded to v1.13.01 (from v1.09.04). After figuring out that I need to supply the '-standalone' switch now (I'm using LiteStep to launch FARR on WIN+D) I've run into a serious problem: Incremental search doesn't work anymore.
FARR doesn't attempt to search for matches when I enter some characters, and pressing RETURN just launches the first result of the history (let's call that behaviour State_A). If I disable "Incremental search on each keypress" it works as intended. Enabling the option again while FARR is still running (or disabling it, restarting FARR and enabling it afterwards) returns to State_A.

--> Interesting: I've started FindAndRunRobot.exe without any command line parameters now.
Method_1 = Doubleclicking the tray icon
Method_2 = Right-clicking the tray icon and choosing "Show Find and Run Robot (hit break key)"
Method_3 = FindAndRunRobot.exe -standalone

Method_1 opens FARR, displaying the history and performing incremental searches without any problems.
Method_2 opens FARR without history and without incremental searching. Entering something and pressing return causes FARR to search for that keyword, afterwards FARR is in State_A (i.e. changing the search phrase and pressing RETURN launches the first item instead of starting a new scan).
Method_2 + opening and closing the options without any changes suddenly reveals the history, and FARR is in State_A.
Method_2, entering something, pressing RETURN and clicking the options button while it is still scanning causes a deadlock (hour glass cursor and no reaction on any input, but 0% CPU and apparently it can still redraw its window when its dragged out of the screen and back). --> Not reproducable.

--> Interesting, too:
Method_1, entering an alias: All items are displayed as usual.
Method_2, entering an alias and pressing RETURN: All items are displayed as usual. Well, almost. The list has the right number of entries (as far as I can guess from the height of the list), the entries are in the right order, I can right-click them or drag&drop them whereever I want - but they are all invisible (plain white with no icons and no focus rectangles). FARR is in State_A.
Method_3, disabling "Incremental search on each keypress", entering an alias and pressing RETURN: The same as for Method_2, but FARR doesn't get into State_A (i.e. I can enter a new search and pressing RETURN will search for that keyword unless it's an alias (in which case FARR displays its invisible items (ingenious alliteration) again)).

Anything else you'd like me to try? :huh:

/edit: If you can provide the last two betas I'll happily try them to find out which version introduces the bugs.

mouser:
thank you for the report Jan, it looks like some of my recent tweaks are not properly being invoked in methods 2+3.  your description is very clear and i'll try to have a fix up by tomorrow or weds. at the latest.

jdmarch:
Mouser, my subjective impression is that 1.13 is slightly slower than 1.11, and that I lose more initial keystrokes with it than with 1.11. But this really is a subjective impression, quite possibly misleading; my workflow and system load are quite variable, and because I generally use FARR without thinking about it (a tribute to what an elegant and useful program it is), I don't remember anything about it when I don't miss any keystrokes, and generally even when it missed a keystroke,  don't remember how quickly I was typing. (But that said, I don't think I missed any keystrokes in my days with 1.11, and I've definitely missed a few with 1.13).

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version