DisplayFusion v3.0 Beta 22 Released! (v2.2.122)

WARNING: You currently have Javascript disabled!
This website will not function correctly without Javascript enabled.

I have decided to release another beta instead of the final build, just to make sure all the game-related kinks have been worked out. These are the changes in Beta 22:

- Pro license validation updates
- Fixed some language files
- Mouse Hook performance improvements
- Taskbars are no longer force-closed when a full screen application takes over - they won't be removed/added/processed though

Updated language files for Beta 22 can be found attached to this post. If you aren't prompted to update you can download Beta 22 from here:
http://www.binaryfortress.com/Data/Download/?package=displayfusion&beta=1

Important Note: I am still toying with the idea of releasing the final build this Sunday, so if you have any feedback (good or bad) please try to post it by Saturday night at the latest.

Thanks everyone!

• Attachment: it.lang [24,521 bytes]

• Attachment: nl-be.lang [25,349 bytes]

• Attachment: pt-br.lang [25,877 bytes]

• Attachment: sv.lang [25,010 bytes]

• Attachment: zh-cn.lang [21,648 bytes]

Feb 20, 2009 • #1

tassieboy

1 discussion post

I'm loving this - it is already better than the other products doing the same thing.

The only thing I'm really really wanting is the FlashWindowEx hook to be done so I stop missing windows requesting my attention (very annoying with communicators such as MSN Messenger, Pidgin, etc.).

I use this every day and am looking forward to full Win7 support also (it looks very strange on my Win7 box but I'm using a strange build also so I cannot attribute it to DisplayFusion).

Keep up the excellent work - I'm very impressed!

Feb 20, 2009 • #2

Thanks for popping by and giving such great feedback. It's always nice to hear something positive after being buried in bug reports for the last 3 months.

The FlashWindowEx thing is definitely something I have been playing with, as I miss the notifications as well. I haven't been able to work out a reliable way to read this state, but I am working on it for a future release (not for 3.0).