XYplorer Beta Club

v0204 works ok for me on XP.

Yep me too.

admim wrote:XP support is as full as it gets. Done already

Just updated to 18.60.0202 and "Redirect typing to LFB" is now working again on XP and 8.1, no dramas. Thanks very much.

Also, no runtime errors here.

Hi Don, Windows works in mysterious ways and not always according to the manual. :titter: It’s entirely up to you of course, but I would not want to add anything into XY just to support an ancient OS. That sort of thing that makes software maintenance a nightmare. If you want to leave it like it is ...

admin wrote:Can you describe the details of "does not work for me"?

When I type in the LV, nothing happens. XY does not appear to respond in any way. If I turn off "Redirect typing to LFB" then type ahead find functions normally.

admin wrote:Sure about your version numbers?

Yes. 18.60.0103 works ok on XP. 18.60.0104 and 18.60.0105 do not. They all work ok on 8.1. Interesting...

jupe wrote:...does it work in a fresh profile?

No. Weird.

I probably should have said that this is on XP, not 8.1 as in my sig. I will check 8.1 when I get home.

Hi All,

"Redirect typing to Live Filter Box" does not work for me in 18.60.0104 beta. Switching back to 18.60.0103 beta and it works again.

Anyone else?

Cheers
John

I'm using the tweak to show age circle in the modified column, but the circle is now clobbering the date itself. This makes the date hard to read. See screenshot.

Cheers

Same here.

This is very curious. :? I have been conducting some experimentation and can reproduce at will. The problem is seems to only occur on Win XP (my work machine) and on a network folder that is accessed by drive letter (but not in the '\\<server-name>' form). before.PNG In this folder: \\tsiwdcgffs001\...

Same here.

Also, starting with /ini=<path to ini file> causes XY to tell me that my trial has expired. Something wrong reading the path methinks.

I spoke too soon. It started doing it again.

No I didn't, but I do now. Thanks for the heads up.

I fixed my issue. 8) After much mucking about I ended up setting the "Allowed number of entries in the action log" to the maximum value of 256 (it was set to 100) and the problem went away. Perhaps my action log was corrupted in some way, because going back to 100 did not cause the issue t...