DisplayFusion was first released in August of 2007, over 3 years ago! During the last 3 years, DisplayFusion has grown into a must-have utility for anyone with multiple monitors. Licensing has changed as well over the years, with the introduction of a paid Pro version nearly 2 years ago. This paid Pro version was licensed on a per-computer basis, requiring multiple licenses to be purchased for use on multiple computers. After quite a bit of feedback from the DisplayFusion community, I have decided to shuffle the licensing around a little bit.
Starting today, you can now purchase a DisplayFusion Pro Personal Home license. This new license is for home users ONLY, and is not a valid license for company users. The license allows a home user to purchase 1 license, and install it on all of their computers. It's like a mini site license for home users. If you are a home user that has already purchased a DisplayFusion Pro license and you would like to upgrade to a Personal Home license at a discounted price, please contact me.
Another licensing change is a new restriction on free version usage. Starting with version 3.2, the free version of DisplayFusion will no longer be allowed to be used in a company environment. If you are using the free version of DisplayFusion in a company, you have 2 options: keep using 3.1.10 without any restrictions or convince your company to purchase a DisplayFusion Pro license. A single license is just $25, and with multiple licenses you can reduce this to just $15 per license. DisplayFusion needs your support, and every DisplayFusion Pro license purchased will help!
If you have any questions or comments, I encourage you to contact me. If you are using the free version of DisplayFusion, and you can't live without it, why not pitch-in and support the development of future versions? It's only $25 and your purchased license will be valid with all future versions of DisplayFusion!
DisplayFusion 3.1.10 has been released! This is just a small release to address a few issues that slipped through the 3.1.9 release. Here is a quick rundown on the changes in this new version:
I would encourage everyone to update to this new release as soon as possible to take advantage of the improved stability and bug fixes. Thanks everyone!
I am very happy to announce the release of DisplayFusion 3.1.9! Along with this new release, comes the new home of DisplayFusion, located at displayfusion.com. I would like to send out a big thanks to Chris from Sockit Solutions for designing the new website, and for helping getting it off the ground. The new website makes it much easier to look-up information about DisplayFusion, like the Advanced Settings, Support options and, of course, the Downloads.
Now, back to the 3.1.9 release! This release started out as a small release, intended to address a few functionality issues before the major 3.2 release, but it turned into much more than that! There is a big new feature in this release, called the "Windows Logon Background" changer. In the DisplayFusion Settings window, you will see a new tab titled "Windows Logon". You can use this new feature to change your Windows logon background image using local images, or images from one of the online providers (Flickr or Vladstudio). I love this new feature, and I've made sure all of my machines now have custom logon backgrounds.
The Taskbars also received much love. You can now set the Auto-Hide setting on a per-Taskbar basis, as well as disabling Taskbars on a per-monitor basis. The Window Snapping feature received a bit of a makeover, with the addition of a helpful guide to help you set it up in the Settings window. There also a ton, and I mean a ton, of bug fixes. From everything to Taskbar focus issues, to compatibility improvements for over a dozen applications. To see the complete list of changes, I invite you to visit the DisplayFusion Change Log.
If you haven't been prompted to upgrade yet, please visit the DisplayFusion Download page to download the new version today!
Do you love programming? Do you live in the Ottawa area? If you answered yes to both of these questions, I have good news. We want you! We are looking for someone who has at least 3 years experience with C#, and a passion for software development. If you are interested and would like to learn more about this opportunity, please send your resume and contact information (email address and phone number) to jobs@binaryfortress.com. Hope to hear from you soon!
Update: Thank you to everyone who applied, the position is now closed.
If you've ever had to write any interop code to use an unmanaged library in your C# application, you know how tricky it can be to get the data types correct. I often find myself scouring the internet looking for the correct conversions, so I thought I would document everything I have learned so far. This is by no means a comprehensive list of all C++ data types, just the ones I find myself frequently writing interop code for.
C++ Type | C# Type | Size |
---|---|---|
BOOL | bool | 1 byte |
BYTE | byte | 1 byte |
CHAR | byte | 1 byte |
DECIMAL | Decimal | 16 bytes |
DOUBLE | double | 8 bytes |
DWORD | uint, UInt32 | 4 bytes |
FLOAT | float, single | 4 bytes |
INT, signed int | int, Int32 | 4 bytes |
INT16, signed short int | short, Int16 | 2 bytes |
INT32, signed int | int, Int32 | 4 bytes |
INT64 | long, Int64 | 8 bytes |
LONG | int, Int32 | 4 bytes |
LONG32, signed int | int, Int32 | 4 bytes |
LONG64 | long, Int64 | 8 bytes |
LONGLONG | long, Int64 | 8 bytes |
SHORT, signed short int | short, Int16 | 2 bytes |
UCHAR, unsigned char | byte | 1 byte |
UINT, unsigned int | uint, UInt32 | 4 bytes |
UINT16, WORD | ushort, UInt16 | 2 bytes |
UINT32, unsigned int | uint, UInt32 | 4 bytes |
UINT64 | ulong, UInt64 | 8 bytes |
ULONG, unsigned long | uint, UInt32 | 4 bytes |
ULONG32 | uint, UInt32 | 4 bytes |
ULONG64 | ulong, UInt64 | 8 bytes |
ULONGLONG | ulong, UInt64 | 8 bytes |
WORD | ushort | 2 bytes |
void*, pointers | IntPtr | x86=4 bytes, x64=8 bytes |
If I am missing something, or you would like me to include something else, please let me know in the comments below. Thanks!