Hi.

I have a problem when searching.
After multiple searches I'm not able to type anything into the search line anymore. The cursor
blinks and I can select word or the whole line
using pointer, but that's all. Typing in all the other lines works fine.
The only thing I can do to be able to type new searches again is to restart phex, which isn't very happy solution especially when downloading
some huge file I have been searching for quite long. Then it again works for a few searches (5-10).
Where's the problem?

Dano

-----------------
Linux 2.4.5
Phex 0.4.6
Blackdown Java(TM) 2 Runtime Enviroment 1.3.0

Unfortunately I can´t reproduce this on my system (WinME). Perhaps one of the other developers can, but I can´t promise anything.

This is unfortunatly not a phex bug. If it would, it would be fixable.
And this is not limited to the search field. About any object in any swing application under unix can be killed. Other OS seams to handle the alternate key different and don't suffer from this. To check it out Yourself:
-Open phex and an other app.
-Focus a component (for example the search field)
-use mouse to select other app.
-use alt+tab to switch back to phex. Hold alt.
-hold alt and press Q to open a query menu. Or just release both and press tab.
Now the previous selected field has still the focus but is inactive.
It's possible to kill even the focus of buttons and checkboxes but this doesn't hurt as much since they are still useable.
This is a known bug in java and will be fixed with release 1.4.
Tha only advice I have about this: avoid the alt key when working with phex.
When someone can reproduce this and does find a swing application that is under an open source license and has a workaround for this bug please post here.
Alexander

Well, check out phex cvs. The swing problem is still there but most of the time You wont notice. Even more important. After a "good" focus switch phex will recover completely. At least for me. You can't be to sure about all the different X-Servers. There is basicaly an override for the swing focusmanager now. This workaround is inactive for MacOS and windows. If it crashes or behaves worse than before please post here and/or send an email to me.
Alexander