I hate to bring this up as it isn't even a regular conflict (but a conflict within a conflict), however, it seems to emanate from 3.4.1 Betas (I don't know when it started, to be honest, but it's there in .12 yet absent in 3.4.0.

I use Listary free version (http://www.listary.com/) in conjunction with xplorer2 file manager (http://www.zabkat.com/) x64 pro version, and from a cold startup (with DF and Listary both set to start with Windows) for some reason Listary can't hook into x2's panes properly anymore (it works fine in DF 3.4.0).

I tried disabling the compatibility aspects (in DF) of both programmes to nil (even the Listary x86 "helper" module) but to no effect - the only thing that works is to kill DF completely which then instantly allows Listary to hook x2 properly again.

Bizarrely (and just to make it more confusing) Listary hooks into Windows' explorer.exe just fine even under .12, and indeed if I kill the Listary process and restart it then it will hook properly into x2 (but not, as stated, from cold system auto-startup).

Like I said, I hate to mention this, but I spent so much time looking at different versions of all 3 programmes (as well as AV's, etc) before determining DF as the culprit that I'm sure it's part of the recent gaggle of "compatibility" evils Jon no doubt regrets ever taking on. Anyway, as Keith seems to enjoy replicating things, he might have some fun with it...

If t'were to strike me that a world without imagination would strongly resemble a computer with only one monitor - it would follow that a mere and perfunctory topic name would be a subject quite bereft of taste, acumen, and indeed purpose, no? Those who believe the technological milieu is best with its logic, concision, and accuracy will have missed the Divine Comedy for the Principia Mathematica, and in the end, misunderstood them both.

And since that wouldn't be any fun at all, we might as well enjoy our Topics...

Hello Kilmatead and Keith,

I'm the developer of Listary, and I'm also a DF user. Just found this interesting topic and dug into it a bit: I'm 95% sure that you guys forget to call CallNextHookEx in your WH_CBT hook. This not only blocks Listary, but also all other applications that need to detect focus changes in Windows.

Feel free to drop me an email at support@listary.com if you need more information.

What is it about the structure of the human brain that makes me feel guilty when a developer steps up to help, and I'm standing there with me bollix in the the wind saying "Hi, I use the free-version of your software 'cause I'm a cheap bugger". Ok, fine, I don't actually need the extra functionality, but Channing gets a Christmas Present...

Emotions such as humiliating shame are so impractical.

Cool, thanks for the quick fix.

Beta 13 seems to have solved this dilemma - as usual, thank you very much!