Messages - jballi [ switch to compact view ]

Pages: [1] 2 3 4 5next
1
Find And Run Robot / FARR window slowly increases height
« on: November 30, 2007, 11:59 AM »
FARR v2.00.145

I use FARR in the upper left corner of screen (fixed size).  I try to size the window so that it fits the maximum number of search values (9 for me).  I noticed that the FARR window get increasingly taller (not wider) the more I use the program.  The size changes are not immediate but after a bunch of runs the window will increase ever so slightly.  For me it takes 3 or 4 days of use before I say "Doh!" and resize the window back to the desired size.

Not a serious bug but I thought I would report it.

BTW, I use the LE4-Default skin just in case it matters.

Thanks for your attention.

2
sounds reasonable -- i'll add back the option to use tab as normal, and alt+tab for autocomplete.

taichi has earned himself several feature requests, so anyone who can get taichi to support their request will find it on the todo list :)

Thanks.  I think you'll make a lot of keyboard freaks like me a bit happier. :)

But and however, I'm fairly certain that you don't want to use Alt+Tab as an alternative to autocomplete since Alt+Tab already has a built-in system function. :o

Them be my thoughts...

3
yes, jbali this was a recent change.
my reasoning was that the down arrow key can be used in edit box to switch to results view, and escape from results brings you back up to edit box, so i thought we could use tab for autocomplete.

Thanks for the quick reply.

Any chance of adding an option to return the tab functionally back to way it worked before?  ...and/or allowing to user to determine which keys (or key combinations) will be used for what function.   For example: Ctrl+Tab for autocomplete.

I only make a fuss because I'm a big keyboard user and for a form of this type (Edit field followed by a List field), the natural way to navigate from the Edit field to the List field (at least for me) is the tab key.

Thank you for your consideration.

4
v2.00.120

Please please please tell me, when did we stop using the tab key for navigation and started using it only for entering parameters!  I spent 20 minutes looking for a configuration parameter to return this function back to how it worked before but couldn't find anything.  It worked fine on the last version I tested (v2.00.083).

Hep me.  Everyone needs hep every once in while.

Thanks.


Edit:  Just for clarification...  For me the tab key would normally take to the first item in the list.  I would then use the up/down key for additional navigation.

5
Find And Run Robot / Re: Odd startup bug
« on: May 17, 2007, 09:12 PM »
Re: Odd startup bug.  Original post: https://www.donationcoder.com/forum/index.php?topic=6624.msg60160#msg60160

The mysterious holding down of ALT is a classic problem that I used to get a lot in windows before XP. Now it just happens to me every year or something. I notice that your FARR shortcut has an ALT in it so pressing that could start and stop the odd behaviour.
-QuickBrownFox

Thank you for your interest.  I've delayed replying to your post because I wanted the bug to occur again several times so I could do some additional testing...


-Does the problem disappear when you press the ALT key?
-QuickBrownFox

No.  When in the middle of this "bug" (for lack of a better word), almost all input is blocked.  Like a stated earlier, the program acts as though the ALT key is being pressed down.  Pressing the ALT key doesn't change anything.


-When this problem occurs, go to another application (NOT by alt-tab) and press a key. Does the behaviour persist?
-QuickBrownFox
To be honest, I never thought to try to run other applications while FARR is running.  After all, there is no reason to have the FARR window active unless you want it to do stuff.

In a effort to track down this problem, I did have an opportunity to give this a try and... When I clicked to other windows and did stuff (no input block problems) and returned back to the FARR window, the input block was gone.


Just thought I'd point out that it's not necessarily FARR's fault and it could be windows or even the keyboard.
-QuickBrownFox
At this point there is no definitive proof that this is a FARR bug/problem.  However, since this idiosyncrasy only occurs while the FARR window is active (no problems with any other windows, ever), I have to conclude that this is probably a FARR bug.  Of course, if no one else experiences the problem and/or the bug cannot be reproduced, there is not much that can be done.

Thank you for your consideration.

Pages: [1] 2 3 4 5next
Go to full version